Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Saturday 22 August 2009 02:40:53 Scott Schappell wrote: On Aug 21, 2009, at 17:32:13, Mel Flynn wrote: On Friday 21 August 2009 07:34:11 Scott Schappell wrote: 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 r...@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. There should be a backtrace in info.0 already. That part contains more relevant information. Nope, that's all info.0 contains. Follow up. Temp fix available here: http://www.freebsd.org/cgi/getmsg.cgi?fetch=193338+0+current/freebsd-current -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On August 20, 2009, Scott Schappell wrote: I cannot get the system to generate a dump, even though dumpon verified it's set to the swap drive but /var/crash stays empty. I have dumpdev=AUTO in rc.conf and dumpdir=/var/crash as well. If you don't have it already, you may also need ddb_enable=YES savecore_enable=YES Cheers, -- Norbert Papke. npa...@acm.org http://saveournet.ca Protecting your Internet's level playing field ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
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 r...@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 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Friday 21 August 2009 07:34:11 Scott Schappell wrote: 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 r...@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. There should be a backtrace in info.0 already. That part contains more relevant information. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Tuesday 18 August 2009 12:11:10 Tim Judd wrote: On 8/18/09, Scott Schappell arc...@silvertree.org wrote: I have a drive (/dev/ad2s1d) mounted to /backup that I want to be read only until the backup scripts run and then it will be read/write. If I set /etc/fstab to: /dev/ad2s1d /backup ufs ro 0 0 On my CF-based devices (firewalls.. nagios boxes, etc), I run: mount -uw / to update the mount (not mount again) the filesystem. If you're trying to mount again, I could understand why the box panics. I don't. It's perfectly valid to mount a device multiple times and on the same node even. Certainly unmounting then remounting should not panic the system. If you keep getting this panic, please try and obtain a crash dump, though I suspect this to be driver or hardware related as I can't imagine such a bug has slipped into vfs/ufs. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Thursday 20 August 2009 15:00:48 Scott Schappell wrote: On Aug 20, 2009, at 15:42:05, Mel Flynn wrote: I don't. It's perfectly valid to mount a device multiple times and on the same node even. Certainly unmounting then remounting should not panic the system. If you keep getting this panic, please try and obtain a crash dump, though I suspect this to be driver or hardware related as I can't imagine such a bug has slipped into vfs/ufs. -- Mel Since using the mount -r syntax, it hasn't crashed once. How does one obtain a crash dump? I'll be happy to force the system to hork and send a crash log. http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On 8/20/2009 4:31 PM, Mel Flynn wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html OK, /backup was mounted read only, I did the following umount /backup mount -o rw /backup [r...@arthur ~]# dd if=/dev/zero of=/backup/testfile bs=1024 dd: /backup/testfile: end of device 21122+0 records in 21121+0 records out 21627904 bytes transferred in 2.215991 secs (9759924 bytes/sec) [r...@arthur ~]# You can see by that snippet it barfed at 21627094 bytes (21 megabytes, ish). /backup has 100s of GiB free. Filesystem SizeUsed Avail Capacity Mounted on /dev/ad0s1a9.7G453M8.5G 5%/ devfs 1.0K1.0K 0B 100%/dev /dev/ad0s1d 15G481M 13G 4%/var /dev/ad0s1e 15G3.1G 10G23%/usr /dev/ad0s1f 15G1.4G 12G10%/usr/local /dev/ad0s1g216G3.5G195G 2%/home /dev/ad2s1d226G 32G176G15%/backup I cannot get the system to generate a dump, even though dumpon verified it's set to the swap drive but /var/crash stays empty. I have dumpdev=AUTO in rc.conf and dumpdir=/var/crash as well. Could this have anything to do with how I added the drive? I followed the handbook instructions but maybe I messed it up. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On 8/20/2009 7:36 PM, Scott Schappell wrote: On 8/20/2009 4:31 PM, Mel Flynn wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html OK, /backup was mounted read only, I did the following umount /backup mount -o rw /backup [r...@arthur ~]# dd if=/dev/zero of=/backup/testfile bs=1024 dd: /backup/testfile: end of device 21122+0 records in 21121+0 records out 21627904 bytes transferred in 2.215991 secs (9759924 bytes/sec) [r...@arthur ~]# As of now, the dd command above has not crashed and it's past 3 GiB, using the mount -u -w syntax versus unmount, mount -o rw. This is puzzling. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Thursday 20 August 2009 18:40:27 Scott Schappell wrote: On 8/20/2009 7:36 PM, Scott Schappell wrote: On 8/20/2009 4:31 PM, Mel Flynn wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/ker neldebug.html OK, /backup was mounted read only, I did the following umount /backup mount -o rw /backup [r...@arthur ~]# dd if=/dev/zero of=/backup/testfile bs=1024 dd: /backup/testfile: end of device 21122+0 records in 21121+0 records out 21627904 bytes transferred in 2.215991 secs (9759924 bytes/sec) [r...@arthur ~]# As of now, the dd command above has not crashed and it's past 3 GiB, using the mount -u -w syntax versus unmount, mount -o rw. This is puzzling. I agree. These errors make no sense to me, which leads me to drive cable or physical memory problems, perhaps filesystem corruption. Since you have plenty of space on /home, is it possible for you to move whatever's on /backup to /home, then newfs /backup? Of course you could try fsck -y /backup in single user, but with these weird errors, I trust the filesystem on that disk as far as I can throw it. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Remounting a drive as read/write crashes the system and no dmesg.boot
I have a drive (/dev/ad2s1d) mounted to /backup that I want to be read only until the backup scripts run and then it will be read/write. If I set /etc/fstab to: /dev/ad2s1d /backup ufs ro 0 0 to mount it read only most of the time then do: umount /backup mount -o rw /backup the system crashes, it just reboots about 10 seconds into writing data. The system is perfectly stable with it mounted read/write. Also, dmesg.boot has completely disappeared from the system, and touch /var/log/dmesg.boot it does not get populated. # uname -a FreeBSD arthur.silvertree.org 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/ obj/usr/src/sys/ARTHUR i386 Any suggestions on the remounting drive and dmesg.boot? Thanks! Scott P.S. It's good to be off of FreeBSD 4.11 :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On 8/18/09, Scott Schappell arc...@silvertree.org wrote: I have a drive (/dev/ad2s1d) mounted to /backup that I want to be read only until the backup scripts run and then it will be read/write. If I set /etc/fstab to: /dev/ad2s1d /backup ufs ro 0 0 On my CF-based devices (firewalls.. nagios boxes, etc), I run: mount -uw / to update the mount (not mount again) the filesystem. If you're trying to mount again, I could understand why the box panics. Try in your script: mount -u -w /backups or shorter by a little: mount -uw /backups do your stuff, then go back to read-only: mount -ur /backups HTH to mount it read only most of the time then do: umount /backup mount -o rw /backup the system crashes, it just reboots about 10 seconds into writing data. The system is perfectly stable with it mounted read/write. Also, dmesg.boot has completely disappeared from the system, and touch /var/log/dmesg.boot it does not get populated. # uname -a FreeBSD arthur.silvertree.org 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Fri Aug 14 13:27:47 PDT 2009 r...@arthur.silvertree.org:/usr/ obj/usr/src/sys/ARTHUR i386 Any suggestions on the remounting drive and dmesg.boot? Thanks! Scott P.S. It's good to be off of FreeBSD 4.11 :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Remounting a drive as read/write crashes the system and no dmesg.boot
On Aug 18, 2009, at 13:11:10, Tim Judd wrote: On my CF-based devices (firewalls.. nagios boxes, etc), I run: mount -uw / to update the mount (not mount again) the filesystem. If you're trying to mount again, I could understand why the box panics. Try in your script: mount -u -w /backups or shorter by a little: mount -uw /backups do your stuff, then go back to read-only: mount -ur /backups HTH We have a winner. I am sheepish in admitting I didn't read the man page well enough for mount. Thanks for the answer! Scott ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
