Hi Melmi. Am 04.07.2008 um 23:15 schrieb Melmi:
> Hi folks, > > when my computer crashed last time, the jfs mounted drives claimed > that the fs is "clean" on the next reboot. However, some data was > found in files were it didn't belong. My browser bookmarks, for > example, went into the configuration file of an email application > (and therefore messed it up). > > Now I'm wondering: > When the computer just crashes, is it ok for jfs to call the fs > "clean" on the next reboot? > How come that data moves into places it doesn't belong to? > Is there any chance to prevent such thing to happen? > Is there any chance to figure out which files have been corrupted > so that the last backup may be used? > > System is Debian Etch, to be honest in an sophisticated > configuration;) > Partition 1, Software Raid, ReiserFS, mounted on / > Partition 2, Software Raid, CryptoFS, JFS, mounted on / > cryptofs_mountpoint > > Output from the first boot after the crash is below. > > Thanks in advance for any information, > > Melmi > > Exerpt from Kernellog: > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: replayed 924 > transactions in 11 seconds > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: Using r5 hash to > sort names > Jul 2 07:35:36 playstation kernel: VFS: Mounted root (reiserfs > filesystem) readonly. > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: Removing [71 > 7323 0x0 SD]..done > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: Removing [71 > 7321 0x0 SD]..done > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: Removing [71 > 7320 0x0 SD]..done > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: Removing [71 > 7319 0x0 SD]..done > Jul 2 07:35:36 playstation kernel: ReiserFS: md1: There were 5 > uncompleted unlinks/truncates. Completed > Jul 2 07:35:36 playstation kernel: JFS: nTxBlock = 8192, nTxLock = > 65536 > > Exerpt from bootlog: > Wed Jul 2 07:35:05 2008: Setting parameters of disc: (none). > Wed Jul 2 07:35:05 2008: Activating swap...done. > Wed Jul 2 07:35:05 2008: Checking root file system: /dev/ > md1...fsck 1.40-WIP (14-Nov-2006) > Wed Jul 2 07:35:05 2008: Filesystem seems mounted read-only. > Skipping journal replay. > Wed Jul 2 07:35:05 2008: Checking internal tree..finished > Wed Jul 2 07:35:05 2008: Reiserfs super block in block 16 on 0x901 > of format 3.6 with standard journal > Wed Jul 2 07:35:05 2008: Blocks (total/free): 4885744/1013142 by > 4096 bytes > Wed Jul 2 07:35:05 2008: Filesystem is NOT clean > Wed Jul 2 07:35:05 2008: Reiserfs super block in block 16 on 0x901 > of format 3.6 with standard journal > Wed Jul 2 07:35:05 2008: Blocks (total/free): 4885744/1013142 by > 4096 bytes > Wed Jul 2 07:35:05 2008: Filesystem is NOT clean > Wed Jul 2 07:35:05 2008: done. > Wed Jul 2 07:35:05 2008: Setting the system clock.. > Wed Jul 2 07:35:06 2008: Cleaning up ifupdown.... > Wed Jul 2 07:35:06 2008: Loading kernel modules...done. > Wed Jul 2 07:35:06 2008: Loading device-mapper support. > Wed Jul 2 07:35:06 2008: Generating udev events for MD arrays...done. > Wed Jul 2 07:35:06 2008: Starting early crypto disks... cryptofs > (starting) cryptofs (started)done. > Wed Jul 2 07:35:18 2008: Starting remaining crypto disks...done. JFS also detected during this boot that the filesystem is not clean otherwise it wouldn't have started fsck.jfs > Wed Jul 2 07:35:18 2008: Checking file systems...fsck 1.40-WIP (14- > Nov-2006) > Wed Jul 2 07:35:25 2008: fsck.jfs version 1.1.11, 05-Jun-2006 > Wed Jul 2 07:35:25 2008: processing started: 7/2/2008 7.35.18 > Wed Jul 2 07:35:25 2008: The current device is: /dev/mapper/cryptofs > Wed Jul 2 07:35:25 2008: Block size in bytes: 4096 > Wed Jul 2 07:35:25 2008: Filesystem size in blocks: 73206176 And does Phase 0 of reparing the FS. > Wed Jul 2 07:35:25 2008: **Phase 0 - Replay Journal Log After this step it decided that everything is done and and it stated the FS as clean. > Wed Jul 2 07:35:25 2008: Filesystem is clean. > (<- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!) > Wed Jul 2 07:35:25 2008: done. Hopefully Dave has an idea why Phase 0 wasn't enough in your case. But you could start fsck.jfs manually forcing to go through all check phases. > Wed Jul 2 07:35:25 2008: Setting kernel variables...done. > Wed Jul 2 07:35:25 2008: Mounting local filesystems...done. Regards Michael ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Jfs-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jfs-discussion
