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 Ver
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.
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-RELEAS
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_enabl
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 f
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/zer
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/testf
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
On Tuesday 18 August 2009 12:11:10 Tim Judd wrote:
> On 8/18/09, Scott Schappell 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 /bac
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
On 8/18/09, Scott Schappell 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 (fir
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:
umou
12 matches
Mail list logo
