On Tue, 15 Dec 2009 at 12:16, Jon Nelson wrote:
> An strace of fsck.jfs -n (read only) makes me think that it is still
> replaying the journal.
Well, the manpage states
-n Open the file system read only. Do not replay the
transaction log. Report errors, but do not repair them.
$ mkfs.jfs /dev/loop0
$ dd if=/dev/loop0 | md5sum
39c4ea834c53096bcad355ce5c39f959 -
$ fsck.jfs -n /dev/loop0
$ dd if=/dev/loop0 | md5sum
39c4ea834c53096bcad355ce5c39f959 -
However, when fsck is executed with -f (and -n), it says:
**Phase 0 - Replay Journal Log
[...]
File system checked READ ONLY.
...while the filesystem hasclearely been altered (the checksums differ
too). Maybe the manpage could be updated to say that thes options are
mutually exclusive or something?
Christian.
--
BOFH excuse #47:
Complete Transient Lockout
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
_______________________________________________
Jfs-discussion mailing list
Jfs-discussion@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jfs-discussion
