Is there any way to tell what, if any, changes "e2fsck" has made to the
filesystem or particular files after it has been run (ie. if files were
recovered/fixed/unrecoverable)? Thanks.
_
The new MSN 8: advanced junk mail
following up on the current thread regarding running e2fsck,
under what circumstances would one need to run that command
*manually* on a filesystem that is normally mounted at boot
time? that is, doesn't the boot sequence check the health
of filesystems, and run e2fsck automatically
-BEGIN PGP SIGNED MESSAGE-
Great, just what i was looking for, my script is now a lot smaller.
Patrick
> >Hi,
> >i uses a usb-stick on my laptop. It contains al my important data.
> >Every 20 or 30 mount is ask me to run e2fsck. Because i mount it manually
> >aft
At 18:06 03/12/2002 +0100, you wrote:
-BEGIN PGP SIGNED MESSAGE-
Hi,
i uses a usb-stick on my laptop. It contains al my important data.
Every 20 or 30 mount is ask me to run e2fsck. Because i mount it manually
after boot i wrote a script that count howmany times it has been mounted, and
-BEGIN PGP SIGNED MESSAGE-
Hi,
i uses a usb-stick on my laptop. It contains al my important data.
Every 20 or 30 mount is ask me to run e2fsck. Because i mount it manually
after boot i wrote a script that count howmany times it has been mounted, and
after 20 times it runs automatic
Statux <[EMAIL PROTECTED]> writes:
> The man page for e2fsck says to use -p instead of -a whenever
> possible :)
>
> -Statux
I have seen that ... But that does not change the results!
Anyway, I moved the data out of the way and ran mke2fs again.
This I knew would fix t
The man page for e2fsck says to use -p instead of -a whenever possible :)
-Statux
___
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
I am having this problem where running 'e2fsck -a /dev/hdb1' gives
me:
[root /root] e2fsck -a /dev/hdb1
/dev/hdb1: The filesystem size (according to the superblock) is 4200966 blocks
The physical size of the device is 208813 blocks
Either the superblock or the partition table is li
sorry this happened to you..i wish you must speed and reduced stress getting
things back to normal
Matt Nelson wrote:
> Update: we are screwed.
>
> Note to users of the AMI MegaRAID Enterprise 1500: although a logical
> drive can be expanded w/out requiring a backup/restore, you can only a
Update: we are screwed.
Note to users of the AMI MegaRAID Enterprise 1500: although a logical
drive can be expanded w/out requiring a backup/restore, you can only add
ONE NEW DRIVE AT A TIME. attempting to simultaneously add two or more
new drives to an existing logical volume will result in to
ok, here's the sequence of events:
- the machine is: dual piii/733, 1G, AMI MegaRAID 1500 (RAID 5, four
stripes, 106GB total, 85GB used)
- while attempting to expand a logical drive on the RAID, the controller
failed two of the existing drives, and ignored the two new drives we
were
On Fri, 12 Jun 1998, Iztok Polanic wrote:
> Why doesn't work this:
>
> e2fsck -yt /dev/hdx
e2fsck won't run on a mounted filesystem, you would have to unmount the
filesystem first. Well, it'll run, but I don't think it will do it
non-interactively. It will
> Hello !!!
>
> Why doesn't work this:
>
> e2fsck -yt /dev/hdx
You should only fsck a filesystem when it's unmounted.
> I also tried this:
>
> echo "y" | e2fsck -t /dev/hdx
>
> but it also doesn't worked, because e2fsck is abor
Hello !!!
Why doesn't work this:
e2fsck -yt /dev/hdx
The "y" command should answer to all question yes, but it doesn't.
-y Assume an answer of ``yes'' to all questions;
allows e2fsck to be used non-interactively.
I als
On Mon, 08 Jun 1998, Jake Colman wrote:
>For some unknown reason my machine reported numerous filesystem errors on hdb6
>upon boot and it dropped me into a shell for repair. After poking around a bit
>I tried running 'e2fsck /dev/hdb6', it listed umpteen things it was correct
r. After poking around a bit
> I tried running 'e2fsck /dev/hdb6', it listed umpteen things it was correcting,
> and it seemed to have all worked. The next boot was clean.
>
> Two questions:
>
> 1) This is the second or third time this has happened to me. Is it comm
For some unknown reason my machine reported numerous filesystem errors on hdb6
upon boot and it dropped me into a shell for repair. After poking around a bit
I tried running 'e2fsck /dev/hdb6', it listed umpteen things it was correcting,
and it seemed to have all worked. The nex
o run fsck "MANUALLY (i.e.,
without -a or -p options". So I did (e2fsck /dev/hda4). After several
hundred pages of (if I recall correctly) unattached inodes (I just kept
the "y" key pressed until it was done), it came to
-
David Reed <[EMAIL PROTECTED]> on Sun, Apr 19, 1998 at 11:30:27PM -0600:
> When booting up (running 4.2 with kernel 2.0.32-1.2)
> I get a message about some mount count being exceeded, and needing to run
> e2fsck. Now if I remember correctly, it used run auto-majically at that
On 20-Apr-98 David Reed wrote:
>
> When booting up (running 4.2 with kernel 2.0.32-1.2)
> I get a message about some mount count being exceeded, and needing to run
> e2fsck. Now if I remember correctly, it used run auto-majically at that
> point in the boot sequence...
>
>
When booting up (running 4.2 with kernel 2.0.32-1.2)
I get a message about some mount count being exceeded, and needing to run
e2fsck. Now if I remember correctly, it used run auto-majically at that
point in the boot sequence...
So, how do I get ti back to that state?
What is likely to have
21 matches
Mail list logo
