Date: Fri, 21 Aug 2009 08:34:11 -0700 From: Scott Schappell <archon@silvertree.org> To: Norbert Papke <npapke@acm.org> Cc: freebsd-questions@freebsd.org Subject: Re: Remounting a drive as read/write crashes the system and no dmesg.boot Message-ID: <8CAF5E76-A2E5-4115-BB3F-6A2EC2FB2503@silvertree.org> In-Reply-To: <200908210820.31394.npapke@acm.org> References: <00B06063-9872-4ACE-8767-1221C22E33EE@silvertree.org> <200908201531.06222.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <4A8E0837.5020608@silvertree.org> <200908210820.31394.npapke@acm.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Looking at info.0 I see: Dump header from device /dev/ad0s1b Architecture: i386 Architecture Version: 2 Dump Length: 155131904B (147 MB) Blocksize: 512 Dumptime: Fri Aug 21 08:27:45 2009 Hostname: arthur.silvertree.org Magic: FreeBSD Kernel Dump Version String: FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 root@arthur.silvertree.org:/usr/obj/usr/src/sys/ARTHUR Panic String: ffs_sync: rofs mod Dump Parity: 2778312054 Bounds: 0 Dump Status: good This is interesting: "Panic String: ffs_sync: rofs mod" It looks I'm guessing this is saying "read only file system modified". So it looks like the problem is with mount? If there's anything you want me to pull from the vmcore.0 let me know. Again, this happens with the drive mounted RO from fstab. Unmounted then mount -o rw /backup. Something is amiss, and first blush doesn't seem to be hardware related. Scott
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8CAF5E76-A2E5-4115-BB3F-6A2EC2FB2503>