On Wed, 2003-11-26 at 19:37, Matthias Andree wrote:
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one
ext2
file system on another ATA drive and one ext2 file system on a
On Thu, 27 Nov 2003, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 19:37, Matthias Andree wrote:
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one
ext2
file system on
On Thu, Nov 27, 2003 a.d., Bruce Evans wrote:
This is a known problem for nearly three months now (See PR 56675). It
happens to me every time I shut down the system if i don't unmount my
(read-only) ext2 file systems manually.
I'm not sure if the problem is known for the read-only case.
On Thursday 27 November 2003 10:43, Stefan Ehmann wrote:
On Wed, 2003-11-26 at 19:37, Matthias Andree wrote:
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one
ext2
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one ext2
file system on another ATA drive and one ext2 file system on a SCSI
drive. Both ext2 file systems had been mounted
Date: Wed, 26 Nov 2003 19:37:45 +0100
From: Matthias Andree [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one ext2
file
Matthias Andree wrote:
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
This is easy to reproduce, but apparently uninteresting to the developers:
Reboot to single user, run full fsck, halt.
--
:{ [EMAIL PROTECTED]
Andy Farkas
In message [EMAIL PROTECTED], Kevin Oberman writes:
Date: Wed, 26 Nov 2003 19:37:45 +0100
From: Matthias Andree [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file
Kevin Oberman [EMAIL PROTECTED] writes:
Date: Wed, 26 Nov 2003 19:37:45 +0100
From: Matthias Andree [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems
In a message written on Thu, Nov 27, 2003 at 04:52:04AM +1000, Andy Farkas wrote:
Matthias Andree wrote:
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
This is easy to reproduce, but apparently uninteresting to the developers:
Reboot to
On Wednesday 26 November 2003 19:37, Matthias Andree wrote:
Hi,
when I rebooted my 5.2-BETA (kernel about 24 hours old), it gave up on
flushing 4 dirty blocks.
I had three UFS1 softdep file systems mounted on one ATA drive, one ext2
file system on another ATA drive and one ext2 file system
I'll also note in my FreeBSD current debugging of some drivers it was
about a 50/50 shot as to if this would happen. Having to fsck every
other reboot was only made less painful by the background fsck thing.
Don't some BIOS' protect the superblocks as a kind of virus protection?
Could this be
Ryan Sommers wrote:
I'll also note in my FreeBSD current debugging of some drivers it was
about a 50/50 shot as to if this would happen. Having to fsck every
other reboot was only made less painful by the background fsck thing.
Don't some BIOS' protect the superblocks as a kind of virus
13 matches
Mail list logo
