On Fri, 2005-04-22 at 12:13 -0700, Scott Fritzinger wrote:
> All,
> 
> I'm running into a problem with JFS and needed some pointers.
> 
> I have two 2TB RAID5 arrays on a 3Ware 7000-series controller on a test 
> machine here running 2.6.7-1-386 (stock Debian testing kernel). Both 
> arrays were scanned throroughly using badblocks and have JFS filesystems 
> on them created using:
>       mkfs.jfs /dev/sdc1
>       mkfs.jfs /dev/sdd1
> 
> I mounted them to /mnt/sdc1 and /mnt/sdd1 respectively, added entries to 
> fstab, and didn't have any problems until the machine went down due to a 
> power outage. I brought the machine back up and it didn't mount either 
> of the arrays. I tried to manually mount them:
>       mount /mnt/sdc1
> 
>   and it said it couldn't find a valid filesystem. I thought maybe fstab 
> entries were screwed up, so I provided all the flags:
>       mount -t jfs /dev/sdc1 /mnt/sdc1
> 
> and it still said it couldn't find a valid filesystem. So, I did an fsck:
>       # jfs_fsck /dev/sdc1
>       jfs_fsck version 1.1.7, 22-Jul-2004
>       processing started: 4/22/2005 13.56.25
>       Using default parameter: -p
>       The current device is:  /dev/sdc1
>       Block size in bytes:  4096
>       Filesystem size in blocks:  488386032
>       **Phase 0 - Replay Journal Log
>       Filesystem is clean.
> 
>       # jfs_fsck /dev/sdd1
>       jfs_fsck version 1.1.7, 22-Jul-2004
>       processing started: 4/22/2005 14.2.13
>       Using default parameter: -p
>       The current device is:  /dev/sdd1
>       Block size in bytes:  4096
>       Filesystem size in blocks:  488386032
>       **Phase 0 - Replay Journal Log
>       Filesystem is clean.
> 
> Then, issuing "mount /mnt/sdc1" and "mount /mnt/sdd1" worked as expected 
> and everything was there. Now, as a test (because I'm sure that this 
> isn't how JFS is supposed to work), I made sure the computer was idle 
> and pulled the plug. When it came back up, same thing (no mounts, had to 
> run jfs_fsck to get them mounted). Now, I just reboot and the same thing 
> (no mounts, so run jfs_fsck and mount).
> 
> Because jfs_fsck isn't reporting any bad entries, it seems like it is 
> just replaying the journal, but should that happen when attempting to 
> mount the device? Am I missing something? I had XFS on these same arrays 
> before JFS and didn't run into anything like this (we are evaluating 
> different FS's).

The code to replay the journal is in /sbin/jfs_fsck, not in the mount
code.  The entries in /etc/fstab should have a non-zero value in the
last field (usually 2).  If fstab is set up this way, the init scripts
should be running fsck against the partitions before it attempts to
mount them.

> We are planning on moving back down to 2.4.27 on this machine for 
> further testing; would that move potentially resolve issues or create more?

That shouldn't make any difference.

> Any help is greatly appreciated!
-- 
David Kleikamp
IBM Linux Technology Center



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Jfs-discussion mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jfs-discussion

Reply via email to