similar to: JFS DEBUG: (journal.c, 549)

Getting this warning compiling on an alpha, is it a problem? 2.4.15-pre4 gcc -D__KERNEL__ -I/usr/users/donjr/linux-2.4.15-pre4/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev5 -Wa,-mev6 -DEXPORT_SYMTAB -c journal.c journal.c: In function `journal_init_inode': journal.c:758: warning: long long

I updated my kernel from 0.0.3d to 0.0.3e using the "d-e" patch in the 0.0.3e tarball. When I try to boot the new kernel on a machine with an ext3 root filesystem I am getting the message: JFS: Unrecognised features on journal Does this sound feasible or even somewhat expected? Is there any interest in me doing some debugging of this? Is there any way to deal with this without

This patch contains the following possible cleanups: - make needlessly global functions static - #if 0 the following unused global functions: - journal.c: __journal_internal_check - journal.c: journal_ack_err - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

This patch contains the following possible cleanups: - make needlessly global functions static - journal.c: remove the unused global function __journal_internal_check and move the check to journal_init - remove the following write-only global variable: - journal.c: current_journal - remove the following unneeded EXPORT_SYMBOL's: - journal.c: journal_check_used_features -

Erm, sheez having alot of problems :( I have just been reading all the archives on the mailing list for the past few hours and decided to try make the journal with: tune2fs -j -J10 /dev/hdc1 [root@tkw /]# tune2fs -j -J10 /dev/hdc1 tune2fs 1.20-WIP, 17-Jan-2001 for EXT2 FS 0.5b, 95/08/09 Creating journal inode: done [root@tkw /]# cat /etc/fstab /dev/hdc1 /usr/local ext3

I would like to run a for loop with an index going from 0 to 499 but the following seems to miss out the first value: C <- 499 for (i in 0:C) The alternative is: C <- 500 for (i in 1:C) { #Then every time I use i, I replace it with i-1 } Is this a good way to do it or is tere a better way? Thank you, ThomasThis message and any attachment are intended solely for the addressee and may

I have installed the xen 3.1.0 x86_64 tarball compiled for RHEL5 on a RHEL5 system. The system in question was able to boot with the xen kernel that came with RHEL5. I untarred the tarball, and did cd /boot mkinitrd /boot/initrd-2.6.18-xen.img 2.6.18-xen The command exited properly and made a initrd image. The machine booted with a grub.conf entry like this: title Xen 3.1.0 root

"IT3 Stuart Blake Tener, USNR-R" wrote: > In terms of enterprise reliability, I understand, however, having an > "office recommended journaling filesystem", Some journaling filesystems can be _worse_ than non-journaled. If the recovery mechanism of the JFS is to "aggressively" go to the journal, journal mis-reads can _toast_ a filesystem. I'll take a full

Hello I run the latest kernel from centosplus and use a JFS partition. Even though the jfs tools are installed, when the server crashes, it doesn't run fsck.jfs automatically when at boot time it detects that the partition is corrupted I have to run fsck.jfs manually and mount the drive. Is there a way to make fsck.jfs run automatically if required ? (I recently moved from Fedora to

Hello. I''ve built a kernel from git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git (Date: Fri Nov 19 19:46:45 2010 -0800) and got a kernel oops when tried to access to unplugged, but mounted external usb storage formatted with JFS. Steps to reproduce: mkfs.jfs /dev/sdb1 (unpluggable USB hard drive) mount /dev/sdb1 /mnt/drive cd /mnt/drive touch test sync

Does it have posix acls enabled? The details on http://mirror.centos.org/centos/4/centosplus/Readme.txt only mention basic read and write support.

Here's a patch to support JFS in fstype. Given that this runs as root, would you consider a patch to take the device as an argument rather than stdin? I get really nervous that one of these days I'm going to > rather than <. But otherwise... =) Tested against 1.0.14, but there's nothing in there that should keep it from applying against current git that I can see. Tks, Jeff

[please note that I'm not subscribed to the list] Hi guys, I've noticed that the size returned by the fstype utility was not correct for JFS filesystems (it returns the size in number of HW blocks instead of bytes). Here is a simple patch that addresses it (based on 1.5.7 from the debian package). diff -Nur klibc-1.5.7.orig/usr/kinit/fstype/fstype.c

I've tested all these filesystems here: http://rwmj.wordpress.com/2009/11/08/filesystem-metadata-overhead/ -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top -------------- next part

Hi folks... trying to pick between jfs and xfs for a filesystem. In the past we've used jfs with CentOS + centosplus, however, an older post indicated that this may not be the best choice as the version of jfs included with the centosplus kernel would only be as new as the version that was included in the 2.6.18 kernel as RH doesn't backport fixes... It looks like xfs isn't part of

yum -y install http://mirrors.coreix.net/elrepo/elrepo/el6/x86_64/RPMS/kmod-jfs-0.0-1.el6.elrepo.x86_64.rpm (that's for 64bit, adjust the url accordingly for 32bit) it won't hose your system -- Sent from the Delta quadrant using Borg technology! Nux! www.nux.ro ----- Original Message ----- > From: "H" <agents at meddatainc.com> > To: "CentOS mailing

A couple of days ago I submitted a request to ElRepo and kmod-jfs is now available for CentOS 7 as well. On 04/12/2017 12:58 AM, H wrote: > Thank you, installed it and it worked fine. Now I am looking for the same for CentOS 7... It did not look like you have that in your repository? > > > On 3/13/2017 1:09 PM, Nux! wrote: >> yum -y install

On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: > On 04/18/2017 12:54 PM, H wrote: > > A couple of days ago I submitted a request to ElRepo and kmod-jfs is > now available for CentOS 7 as well. > > > > Did not have a need to mount a JFS disk on my CentOS 7 system until today > and it does not want to be mounted, instead complaining

On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> wrote: > >On Thu, Oct 26, 2017 at 3:11 PM, H <agents at meddatainc.com> wrote: > > > >> On 04/18/2017 12:54 PM, H wrote: > >> > A couple of days ago I submitted a request to ElRepo and kmod-jfs >

On Thu, Oct 26, 2017 at 5:22 PM, H <agents at meddatainc.com> wrote: > On 10/26/2017 08:01 PM, Akemi Yagi wrote: > > On Thu, Oct 26, 2017 at 4:17 PM, H <agents at meddatainc.com> wrote: > > > >> On October 26, 2017 6:31:04 PM EDT, Akemi Yagi <amyagi at gmail.com> > wrote: > >>> On Thu, Oct 26, 2017 at 3:11 PM, H <agents at