-- Joey Kelly < Minister of the Gospel | Computer Networking Consultant > http://joeykelly.dhs.org "When Government fears the people, it's liberty. When people fear the Government, it's tyranny." -- Benjamin Franklin Ich möchte ein Berliner.
attached mail follows:
Hello,
I have a samba server that serves up CD images at work via directories
mounted as loop devices. We lost power this morning, and now on boot, this
Linux box runs e2fsck on /dev/hda6 (which is the /home partition where the
images are stored). I am getting "block bitmap differences" and then line
after line (screen after screen) of numbers like: -119451 -119452 etc.
I am assuming that I did not have the loop back devices correctly entered or
whatever and so linux is finding some problems with the images.
What I want to know is: Is e2fsck actually fixing anything at this point or
just reporting it. If I let it continue, will it eventually stop?
Any idea how long this might take with an IDE 4500RPM 10GB partition with a
P1-133?
I think I can cancel it by CTRL-Cing, but it I try to start it again it says
/home is mounted. When I try to umount it, it is busy.
Any suggestions anyone?
I wouldn't be the worst thing in the world to just delete those images and
start over, but if it isn't going to fix the problem, I'll wait.
Thanks,
John
___________________
Nolug mailing list
nolug@nolug.org
attached mail follows:
Let it run. It will attempt to fix the errors without user intervention.
If necessary, it will leave stray files in /lost+found . If it
find too many errors, it will drop the box into single user mode and
you'll have run fsck /dev/hda6 by hand which basically means you'll be
tappying the "enter" key a whole lot.
If you're in an environment that has power "issues", in addition to regular
backups, you may want to consider a journalled filesystem. reiserfs,
xfs, and ext3 are available for 2.4 kernels. This will get you booting
back much much quicker following a power failure.
On Thu, Nov 15, 2001 at 01:51:20PM -0600, John Kosta (earthlink.net) wrote:
> Hello,
>
> I have a samba server that serves up CD images at work via directories
> mounted as loop devices. We lost power this morning, and now on boot, this
> Linux box runs e2fsck on /dev/hda6 (which is the /home partition where the
> images are stored). I am getting "block bitmap differences" and then line
> after line (screen after screen) of numbers like: -119451 -119452 etc.
>
> I am assuming that I did not have the loop back devices correctly entered or
> whatever and so linux is finding some problems with the images.
>
> What I want to know is: Is e2fsck actually fixing anything at this point or
> just reporting it. If I let it continue, will it eventually stop?
> Any idea how long this might take with an IDE 4500RPM 10GB partition with a
> P1-133?
>
> I think I can cancel it by CTRL-Cing, but it I try to start it again it says
> /home is mounted. When I try to umount it, it is busy.
>
> Any suggestions anyone?
>
> I wouldn't be the worst thing in the world to just delete those images and
> start over, but if it isn't going to fix the problem, I'll wait.
>
> Thanks,
>
> John
>
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
-- Scott Harney<scotth@scottharney.com> PGP Key fingerprint = 6D 31 C3 00 77 8C D1 C2 59 0A 01 E3 AF 81 94 63 ___________________ Nolug mailing list nolug@nolug.org
attached mail follows:
It will take a while. It might be prudent to at least try to switch to ext3
in the near future.
I had one like this too (it served like 80 or so iso images .. it would've
taken forever to rebuild that if lost) - I just bought another drive and
mirrored them.
Tim Kelley <tpk6 at home.com>
"The three things were damnably clever constructions of their kind,
and were furnished with ingenious metallic clamps to attach them to
organic developments of which I dare not form any conjecture."
-H.P. Lovecraft
----- Original Message -----
From: "John Kosta (earthlink.net)" <johnkosta@earthlink.net>
To: <nolug@nolug.org>
Sent: Thursday, November 15, 2001 1:51 PM
Subject: [Nolug] e2fsck on boot --#####
> Hello,
>
> I have a samba server that serves up CD images at work via directories
> mounted as loop devices. We lost power this morning, and now on boot,
this
> Linux box runs e2fsck on /dev/hda6 (which is the /home partition where the
> images are stored). I am getting "block bitmap differences" and then line
> after line (screen after screen) of numbers like: -119451 -119452 etc.
>
> I am assuming that I did not have the loop back devices correctly entered
or
> whatever and so linux is finding some problems with the images.
>
> What I want to know is: Is e2fsck actually fixing anything at this point
or
> just reporting it. If I let it continue, will it eventually stop?
> Any idea how long this might take with an IDE 4500RPM 10GB partition with
a
> P1-133?
>
> I think I can cancel it by CTRL-Cing, but it I try to start it again it
says
> /home is mounted. When I try to umount it, it is busy.
>
> Any suggestions anyone?
>
> I wouldn't be the worst thing in the world to just delete those images and
> start over, but if it isn't going to fix the problem, I'll wait.
>
> Thanks,
>
> John
>
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
>
___________________
Nolug mailing list
nolug@nolug.org
attached mail follows:
Yes, so,
this e2fsck ran for at least 4 hours yesterday, and was still going when I
left for home.
I arrived this morning and everything looked fine. I rebooted just to see
what would happen and Mandrake came up with no problems.
Has been working fine all day, and will continue working until the power
goes out again. I think the last time I checked, this box had been up for
200+ days.
When I have time I am going to patch up the kernel and install a journaling
file system.
Thanks for everyone's feedback/help/suggestions.
--Johnny
----- Original Message -----
From: Tim Kelley <tpk@iww.org>
To: <nolug@patientcarerx.com>
Sent: Thursday, November 15, 2001 4:43 PM
Subject: Re: [Nolug] e2fsck on boot --#####
> It will take a while. It might be prudent to at least try to switch to
ext3
> in the near future.
>
> I had one like this too (it served like 80 or so iso images .. it would've
> taken forever to rebuild that if lost) - I just bought another drive and
> mirrored them.
>
> Tim Kelley <tpk6 at home.com>
> "The three things were damnably clever constructions of their kind,
> and were furnished with ingenious metallic clamps to attach them to
> organic developments of which I dare not form any conjecture."
> -H.P. Lovecraft
> ----- Original Message -----
> From: "John Kosta (earthlink.net)" <johnkosta@earthlink.net>
> To: <nolug@nolug.org>
> Sent: Thursday, November 15, 2001 1:51 PM
> Subject: [Nolug] e2fsck on boot --#####
>
>
> > Hello,
> >
> > I have a samba server that serves up CD images at work via directories
> > mounted as loop devices. We lost power this morning, and now on boot,
> this
> > Linux box runs e2fsck on /dev/hda6 (which is the /home partition where
the
> > images are stored). I am getting "block bitmap differences" and then
line
> > after line (screen after screen) of numbers like: -119451 -119452 etc.
> >
> > I am assuming that I did not have the loop back devices correctly
entered
> or
> > whatever and so linux is finding some problems with the images.
> >
> > What I want to know is: Is e2fsck actually fixing anything at this
point
> or
> > just reporting it. If I let it continue, will it eventually stop?
> > Any idea how long this might take with an IDE 4500RPM 10GB partition
with
> a
> > P1-133?
> >
> > I think I can cancel it by CTRL-Cing, but it I try to start it again it
> says
> > /home is mounted. When I try to umount it, it is busy.
> >
> > Any suggestions anyone?
> >
> > I wouldn't be the worst thing in the world to just delete those images
and
> > start over, but if it isn't going to fix the problem, I'll wait.
> >
> > Thanks,
> >
> > John
> >
> >
> > ___________________
> > Nolug mailing list
> > nolug@nolug.org
> >
>
> ___________________
> Nolug mailing list
> nolug@nolug.org
___________________
Nolug mailing list
nolug@nolug.org
Received on 01/15/02
This archive was generated by hypermail 2.2.0 : 12/19/08 EST