site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com I looked at this a bit earlier. This code seems to get called when replaying the journal. Would it work to simply mount the filesystem read-only (so as to avoid writes), and then to disable journaling using hfs.util? Or will the kernel insist on replaying the journal even with a read-only fs? Instead of mounting the volume, try just doing fsck_hfs -f -n /dev/disk#s# David _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Wed, 19 Jan 2005, Carsten G Pedersen <Carsten.Pedersen@hasselblad.dk> wrote: Andrew Gallatin <gallatin@cs.duke.edu> wrote on 01/19/2005 10:07:48 PM: Unfortunately yes it does seem to be called when mounting read-only too - I get the same panic when doing a mount_hfs -o rdonly -j with # being the appropriate numbers for the volume in question. This will cause the journal to be ignored and disable any writes. See what errors it returns. If it doesn't show any serious errors, you might remove the -n. This -should- cause the journal (which sounds like it is corrupt) to be discarded, and at that point, you should be able to mount the disk. If that doesn't occur, something Really Weird(tm) is going on. That said, as someone else already mentioned, I'd be tempted to do a block-level backup of the drive to a file on a larger disk using dd before I ran fsck_hfs just to be safe. This email sent to site_archiver@lists.apple.com