This is no answer to the question, although it may be of interest:
There is an on-going discussion on the linux kernel mailing list about speeding
up fsck for ext3, see, e.g.
http://lkml.org/lkml/2008/1/13/3
--
Regards,
Jörg-Volker.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a sub
how much memory it used? If your / fs isn't 1
> > TB, and you have 24 hrs to spend, you could check just that 1 TB
> > filesysem with top (or something) running and see.
>
> I did peak once via ssh while I was running fsck.ext3 (at that
> time which was close to hour 20
T hardware raid.
>
> I don't suppose you know how much memory it used? If your / fs isn't 1
> TB, and you have 24 hrs to spend, you could check just that 1 TB
> filesysem with top (or something) running and see.
I did peak once via ssh while I was running fsck.ext3 (at
On Fri, May 09, 2008 at 06:58:02PM -0400, Mitchell Laks wrote:
> On 07:24 Fri 09 May , NN_il_Confusionario wrote:
> > > * From: "Douglas A. Tutty" <[EMAIL PROTECTED]>
> > >Does anyone know how much memory fsck needs to check a large filesystem?
> In my case, the fsck took about 24 hours -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/09/08 17:58, Mitchell Laks wrote:
> On 07:24 Fri 09 May , NN_il_Confusionario wrote:
>>> * From: "Douglas A. Tutty" <[EMAIL PROTECTED]>
>>> Does anyone know how much memory fsck needs to check a large filesystem?
>>Linkname: Considera
On 07:24 Fri 09 May , NN_il_Confusionario wrote:
> > * From: "Douglas A. Tutty" <[EMAIL PROTECTED]>
> >Does anyone know how much memory fsck needs to check a large filesystem?
>
>Linkname: Considerations when creating ext3 filesystems - Ext4
> URL:
> http://ext4.wiki.kernel.org
> * From: "Douglas A. Tutty" <[EMAIL PROTECTED]>
>Does anyone know how much memory fsck needs to check a large filesystem?
Linkname: Considerations when creating ext3 filesystems - Ext4
URL:
http://ext4.wiki.kernel.org/index.php/Considerations_when_creating_ext3_filesystems#Memory_n
> * From: "Douglas A. Tutty" <[EMAIL PROTECTED]>
>Does anyone know how much memory fsck needs to check a large filesystem?
some (rather old) information is contained in
Linkname: E2fsprogs Release Notes
URL: http://e2fsprogs.sourceforge.net/e2fsprogs-release.html
for example, it s
You say its very slow.
Does anyone know how much memory fsck needs to check a large filesystem?
Does it take more memory for a larger fs in a linear fashion? E.g.
OpenBSD needs 1 MB per 1 GB fs size to fsck. If the box has less memory
than this, fsck hits swap and really slows down.
Is this 1 T
> then nothing
>
> what to do to get some kind of (ascii :)) graphic or other
> feedback as to how it is doing? It just sits there.
>
> fsck.ext3 -yv /dev/sda1
>
> the v here is not very verbose :(.
$ man fsck
[snip]
-C [ fd ]
Display completion/p
.
fsck.ext3 -yv /dev/sda1
the v here is not very verbose :(.
Thanks,
Mitchell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Am 2008-02-02 15:15:36, schrieb Paul Johnson:
> On Feb 2, 2008 11:01 AM, Manon Metten <[EMAIL PROTECTED]> wrote:
> > Before I change something, I would like to know the current
> > setings. How do I find those?
>
> I believe the manual page for tune2fs would be able to tell you how to
> display th
On Feb 2, 2008 11:01 AM, Manon Metten <[EMAIL PROTECTED]> wrote:
> Before I change something, I would like to know the current
> setings. How do I find those?
I believe the manual page for tune2fs would be able to tell you how to
display the current filesystem options.
--
Paul Johnson
[EMAIL PRO
On Feb 2, 2008 2:53 AM, Jan Willem Stumpel <[EMAIL PROTECTED]> wrote:
> After converting my file system to ext3, I thought there would be
> no more lengthy fsck's every 20 or so boot-ups. But they still
> happen.
>
> Some Googling revealed different opinions; some people say "ext3
> does not need p
Hi,
On 2/2/08, Sam Leon <[EMAIL PROTECTED]> wrote:
I set mine for 60 days or 100 mounts.
>
Before I change something, I would like to know the current
setings. How do I find those?
Greetings, Manon.
Jan Willem Stumpel wrote:
After converting my file system to ext3, I thought there would be
no more lengthy fsck's every 20 or so boot-ups. But they still
happen.
Some Googling revealed different opinions; some people say "ext3
does not need periodic fsck's", others say "even with ext3, it is
be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/02/08 04:53, Jan Willem Stumpel wrote:
> After converting my file system to ext3, I thought there would be
> no more lengthy fsck's every 20 or so boot-ups. But they still
> happen.
Correct. That's the primary ext4 design goal.
The benefit of
On 2008-02-02 11:53 +0100, Jan Willem Stumpel wrote:
> After converting my file system to ext3, I thought there would be
> no more lengthy fsck's every 20 or so boot-ups. But they still
> happen.
You can increase the number of mounts between checks with "tune2fs -c",
see tune2fs(8).
> Some Googl
On Sat, 02 Feb 2008 11:53:46 +0100
Jan Willem Stumpel <[EMAIL PROTECTED]> wrote:
Hello Jan,
> After converting my file system to ext3, I thought there would be
> no more lengthy fsck's every 20 or so boot-ups. But they still
> happen.
Even with ext3, I get checks between 30 and 35 boots per part
After converting my file system to ext3, I thought there would be
no more lengthy fsck's every 20 or so boot-ups. But they still
happen.
Some Googling revealed different opinions; some people say "ext3
does not need periodic fsck's", others say "even with ext3, it is
best to fsck every N boots, be
(thanks David for your comments)
I haven't figured-out exactly what the problem is. However, I
have narrowed it down and more-or-less resolved it for the
time being.
On booting my Debian system got something like:
-
[sbin/fsck.ext3 (1) -- /mnt/mdk] fsck.ext3 -a -C0 /dev/hda11
/d
7 (21-Mar-2005)
fsck.ext3: No such device or address while trying to open /dev/sdb6
Possibly non-existent or swap device?
fsck.ext3: No such device or address while trying to open /dev/sda6
Possibly non-existent or swap device?
fsck failed. Please repair manually.
CONTROL-D will exit from this
Hi,
I have more than one experience with losing some
special files from /dev directory after computer pover failure
on ext3 filesystem.
Is this problem of ext3 filesystem or fsck.ext3?
(why the files, which are not changed are corrupted ?)
Sorry, but I have no report from this "session
23 matches
Mail list logo
