> A full report of filesystem lossage is going to be a bit image of a
> filesystem which has failed, at the least, and ideally, a description
> of what operations were in progress at the time it failed.
>
> You could get the latter in the Hurd by running the failing cases
> under
On 18 Dec 2002, Thomas Bushnell, BSG wrote:
> A full report of filesystem lossage is going to be a bit image of a
> filesystem which has failed, at the least, and ideally, a description
> of what operations were in progress at the time it failed.
>
> You could get the latter in the Hurd by running
Philip Charles <[EMAIL PROTECTED]> writes:
> The typescript of an fsck. A mild corruption. A full scale corruption
> means that the floppy cannot be mounted or the network setup. The
> typescript itself is rather scrambled.
You mention a floppy. Are you popping the floppy out in mid-write?
Th
On Mon, 16 Dec 2002, Alfred M. Szmidt wrote:
>File-system trashed a number of times and this seemed to be associated
>with a mounted cdrom. One trashing forced a reboot. Unfortunately the
>typescript file was lost in the following e2fsck.
>
> Could you be more specific how it trashed
Marcus Brinkmann <[EMAIL PROTECTED]> writes:
> On Mon, Dec 16, 2002 at 08:32:18PM -0500, Neal H. Walfield wrote:
> > > Disk hardware guarantees that a sector write can always be completed
> > > even if the power goes out partway through. That means that writing a
> > > single sector *is* always a
[EMAIL PROTECTED] (Neal H. Walfield) writes:
> > Disk hardware guarantees that a sector write can always be completed
> > even if the power goes out partway through. That means that writing a
> > single sector *is* always atomic.
>
> The size of a single sector does not necessarily equal the siz
On Mon, Dec 16, 2002 at 08:32:18PM -0500, Neal H. Walfield wrote:
> > Disk hardware guarantees that a sector write can always be completed
> > even if the power goes out partway through. That means that writing a
> > single sector *is* always atomic.
>
> The size of a single sector does not neces
> Disk hardware guarantees that a sector write can always be completed
> even if the power goes out partway through. That means that writing a
> single sector *is* always atomic.
The size of a single sector does not necessarily equal the size of of
a disk block.
[EMAIL PROTECTED] (Neal H. Walfield) writes:
> > ext2fs should be quite robust: Even pulling the plug at any time should not
> > corrupt the filesystem beyond what e2fsck can repair.
>
> Let us assume that ext2fs writes a block of metadata to disk. In the
> kernel, in the middle of the DMA opera
> ext2fs should be quite robust: Even pulling the plug at any time should not
> corrupt the filesystem beyond what e2fsck can repair.
Let us assume that ext2fs writes a block of metadata to disk. In the
kernel, in the middle of the DMA operation, the kernel panics. There
is no guarantee that e2f
On Mon, Dec 16, 2002 at 04:50:10PM +0100, Marcus Brinkmann wrote:
> ext2fs should be quite robust: Even pulling the plug at any time should not
> corrupt the filesystem beyond what e2fsck can repair.
In my experience it is almost that robust.
When I'm trying to build things the system repeatedly c
On Mon, Dec 16, 2002 at 09:44:06AM -0500, Neal H. Walfield wrote:
> > OK folk, what is causing the problem?
>
> This is not an ext2fs bug; something is causing a Mach panic. The
> reason that your file system has been corrupted is that the data was
> not synch'ed to disk (when Mach panics, it tak
> OK folk, what is causing the problem?
This is not an ext2fs bug; something is causing a Mach panic. The
reason that your file system has been corrupted is that the data was
not synch'ed to disk (when Mach panics, it takes the whole system
down). The correct solution is to fix Mach. Determinin
File-system trashed a number of times and this seemed to be associated
with a mounted cdrom. One trashing forced a reboot. Unfortunately the
typescript file was lost in the following e2fsck.
Could you be more specific how it trashed the filesystem? Output from
e2fsck would be a good st
File-system trashed a number of times and this seemed to be associated
with a mounted cdrom. One trashing forced a reboot. Unfortunately the
typescript file was lost in the following e2fsck.
>From memory,
-something- panic
zalloc: zone threads exhausted.
After installing the packages from the
15 matches
Mail list logo
