Dirk <[EMAIL PROTECTED]> writes:
> fsck.reiser4 --build-fs
>
> result in data loss? I mean to fix the partition - NOT to lose the data
> on it..
>
> The manual page is also not very specific about if data will be lost or
> not when using this option...
The reiserfs fsck is broken by design. It c
On Fri 21 Jul 2006 15:35, Dirk wrote:
> will using
>
> fsck.reiser4 --build-fs
>
> result in data loss? I mean to fix the partition - NOT to lose the data
> on it..
>
> The manual page is also not very specific about if data will be lost or
> not when using this option...
>
> Using --fix resulted
Hello,
will using
fsck.reiser4 --build-fs
result in data loss? I mean to fix the partition - NOT to lose the data
on it..
The manual page is also not very specific about if data will be lost or
not when using this option...
Using --fix resulted in a message that I should use --build-fs to remov
> After an unclean halt, fsck found duplicate blocks on my root partition.
> Unexpectidly, it continues the boot process with root partition mounted
> read-write (instead of asking for root password for maintenance).
running tune2fs -l /dev/hda1 learned me that the "Error behaviour" is set
to "Con
Hi ...
After an unclean halt, fsck found duplicate blocks on my root partition.
Unexpectidly, it continues the boot process with root partition mounted
read-write (instead of asking for root password for maintenance).
Now, I guess the best is to run fsck which requires the root partition to
be mou
matt wrote:
(woody, 2.4.18)
I have a ext2 fs which I converted to ext3, I'm not sure how relavent
that is but when I try to fsck the drive I get an error
fsck 1.27 (8-Mar-2002)
e2fsck 1.27 (8-Mar-2002)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-bl
On Sun, Dec 29, 2002 at 10:25:26PM +1100, matt wrote:
> fsck 1.27 (8-Mar-2002)
> e2fsck 1.27 (8-Mar-2002)
> Couldn't find ext2 superblock, trying backup blocks...
> fsck.ext2: Bad magic number in super-block while trying to open /dev/had
>
> Any ideas ?
You should have ext3 or auto for the filesy
(woody, 2.4.18)
I have a ext2 fs which I converted to ext3, I'm not sure how relavent
that is but when I try to fsck the drive I get an error
fsck 1.27 (8-Mar-2002)
e2fsck 1.27 (8-Mar-2002)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext2: Bad magic number in super-block while try
My machine went loopy yesterday and when I restarted it it claimed I
needed to run interactive fsck to fix things. So I did this, and all
goes fine up to a point - (I say 'y' the fix the problems it throws up)
- but in Pass 5 ("checking summary group information") I am prompted:
"Block bitmap
Jim Foltz wrote:
>
> On Fri, Oct 02, 1998 at 09:33:57AM -0700, Albert Hurd wrote:
> > A power outage just caused a file check failure. I was told to fix the
> > problem manually with fsck. When I run fsck or fsck -r -f, it replies
> > with the usual, "Parallelizing fsck version 1.10 (24-Apr-97)" a
On Fri, Oct 02, 1998 at 09:33:57AM -0700, Albert Hurd wrote:
> A power outage just caused a file check failure. I was told to fix the
> problem manually with fsck. When I run fsck or fsck -r -f, it replies
> with the usual, "Parallelizing fsck version 1.10 (24-Apr-97)" and
> immediately returns me
A power outage just caused a file check failure. I was told to fix the
problem manually with fsck. When I run fsck or fsck -r -f, it replies
with the usual, "Parallelizing fsck version 1.10 (24-Apr-97)" and
immediately returns me to the (root) prompt without doing any repairs.
When I try to reboot
12 matches
Mail list logo
