On Wed, 2007-09-19 at 14:18 +0200, Oliver Neukum wrote: > Am Samstag 08 September 2007 schrieb Dave Kleikamp: > > On Fri, 2007-09-07 at 11:52 +0200, Oliver Neukum wrote: > > > Am Donnerstag 06 September 2007 schrieb Christian Kujau: > > > > On Tue, 4 Sep 2007, Oliver Neukum wrote: > > > > > using jfs on a flash drive (which is a bit unusual: 2K sectors) > > > > > unmounting > > > > > triggers a warning and takes 52 second, if I have used the > > > > > filesystem. (ls -l) > > > > > is sufficient. This is 2.6.23-rc4 on x86_64. > > > > I'm not really sure there's a good reason to have jfs on flash. You > > would probably be better off with jffs2. However, I do want to > > This is a usb storage device. The fs has no idea it is on flash. > A real disk would have the same effect.
OK. I want to figure it out in any case. > > understand what's going on here and figure out how to fix it. > > > > > > Hm, the fs/jfs/jfs_logmgr.c changes in -rc5 were only whitespace > > > > cleanup, so may not be worth a try. > > > > > > 2.6.23-rc5 with JFS_DEBUG: > > > > > > the first try works without error, on the second attempt to mount: > > > > > > oenone:/var/log # tail -2500 /var/log/messages |grep jfs > > > Sep 7 11:50:25 oenone kernel: jfs_mount: diMount(ipaimap2) failed, rc = > > > -5 > > > Sep 7 11:50:25 oenone kernel: jfs_mount failed w/return code = -5 > > Sep 19 14:13:04 oenone kernel: jfs_flush_journal: synclist not empty > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae57b8: 0e161000 00000000 > 000036a0 00002ae6 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae57c8: 508e7f00 ffff8100 > 508e7f00 ffff8100 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae57d8: 00000004 00000000 > 00000000 00000000 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae57e8: 63ad9000 ffff8100 > 00000055 00000000 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae57f8: 00000001 00002ae6 > 63ae5800 ffff8100 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae5808: 63ae5800 ffff8100 > 9f28df78 ffff8100 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae5818: 00001000 0000376c > 00000000 00002ae6 > Sep 19 14:13:04 oenone kernel: metapage: ffff810063ae5828: 508e7e00 ffff8100 > Sep 19 14:13:04 oenone kernel: page: ffff81009f28df78: 010000000000087c > ffffffff00000001 > Sep 19 14:13:04 oenone kernel: page: ffff81009f28df88: ffff810063ae57b8 > ffff810063ae3e28 > Sep 19 14:13:04 oenone kernel: page: ffff81009f28df98: 0000000000000055 > ffff81009f28df68 > Sep 19 14:13:04 oenone kernel: page: ffff81009f28dfa8: ffff81009fc79790 > > Again, this happens on the second umount. I'll have to dig through this to see if it gives me anything to work with. > > Does fsck find any errors? > > fsck 1.40.2 (12-Jul-2007) > fsck.jfs version 1.1.11, 05-Jun-2006 > processing started: 9/19/2007 14.17.38 > Using default parameter: -p > The current device is: /dev/sdd1 > Block size in bytes: 4096 > Filesystem size in blocks: 474269 > **Phase 0 - Replay Journal Log > Filesystem is clean. Please run "fsck -n" against the drive. Thanks, Shaggy -- David Kleikamp IBM Linux Technology Center ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
