From: Ted Ts'o <tytso@mit.edu>
To: Rogier Wolff <R.E.Wolff@BitWizard.nl>
Cc: linux-ext4@vger.kernel.org
Subject: Re: fsck performance.
Date: Sun, 20 Feb 2011 12:09:31 -0500 [thread overview]
Message-ID: <20110220170931.GB3017@thunk.org> (raw)
In-Reply-To: <20110220090656.GA11402@bitwizard.nl>
On Sun, Feb 20, 2011 at 10:06:56AM +0100, Rogier Wolff wrote:
> Debian apparently recently pointed that to the new release squeeze, so
> I got upgraded. I went from kernel 2.6.26 to 2.6.32. After about a day
> my system rebooted without my consent. So now it's running 2.6.32.
>
> Since then I'm getting kernel-oops-lookalikes that start with:
> [71664.306573] swapper: page allocation failure. order:5, mode:0x4020
That's a warning which has been suppressed in newer kernels. Ext4
falls back to vmalloc() if kmalloc() fails, and sometime in the early
2.6.3x kernels the kernel started warning on huge kmalloc failures,
without having a way of suppressing those errors. That's a cosmetic
issue which has been fixed. (It should only be happening at when an
ext4 file system is being mounted, right?)
> Anyway, upon boot into the new kernel ext3 printed abunch of these:
> [ 5.212119] ext3_orphan_cleanup: deleting unreferenced inode 1335743
That's normal if you didn't cleanly umount the file system before
reporting, and there were files that were still open, but deleted at
the time of the crash.
> A few hours later, my storage partition was marked read-only and the
> backups started failing.
>
> kern.log.1.gz:Feb 18 05:39:53 driepoot kernel: [10328.424778]
> EXT3-fs error (device md3): ext3_lookup: deleted inode referenced: 277447722
That's not normal. :-)
> fcntl64(6, F_SETLKW, {type=F_WRLCK, whence=SEEK_SET, start=164, len=1}) = 0
> fcntl64(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=164, len=1}) = 0
>
> So, my question is: Are these fcntl calls neccesary?
> As far as I know locking is neccesary if another process might be
> handling the same data. Here is is doing this with the cache
> files:
>
> lrwx------ 1 root root 64 Feb 20 09:28 5 ->
> /var/cache/e2fsck/123a1cfe-2455-4646-aa32-87492ed1ac97-icount-ayxVou
> lrwx------ 1 root root 64 Feb 20 09:28 6 ->
> /var/cache/e2fsck/123a1cfe-2455-4646-aa32-87492ed1ac97-dirinfo-rBBTtb
Ah, you're using tdb. Tdb can be really slow. It's been on my todo
list to replace tdb with something else, but I haven't gotten around
to it.
No, it shouldn't be necessary given that e2fsck is the only user of
the tdb files. I'll need to look at trying to remove them, but I'm
not sure that would really improve the speed.
- Ted
next prev parent reply other threads:[~2011-02-20 17:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-20 9:06 fsck performance Rogier Wolff
2011-02-20 17:09 ` Ted Ts'o [this message]
2011-02-20 19:34 ` Ted Ts'o
2011-02-20 21:55 ` Rogier Wolff
2011-02-20 22:20 ` Ted Ts'o
2011-02-20 23:15 ` Rogier Wolff
2011-02-20 23:41 ` Ted Ts'o
2011-02-21 10:31 ` Amir Goldstein
2011-02-21 16:04 ` Paweł Brodacki
2011-02-21 18:00 ` Andreas Dilger
2011-02-22 10:20 ` Rogier Wolff
2011-02-22 13:36 ` Rogier Wolff
2011-02-22 13:54 ` Rogier Wolff
2011-02-22 16:32 ` Andreas Dilger
2011-02-22 22:13 ` Ted Ts'o
2011-02-23 4:44 ` Rogier Wolff
2011-02-23 11:32 ` Theodore Tso
2011-02-23 20:53 ` Rogier Wolff
2011-02-23 22:24 ` Andreas Dilger
2011-02-23 23:17 ` Ted Ts'o
2011-02-24 0:41 ` Andreas Dilger
2011-02-24 8:59 ` Rogier Wolff
2011-02-24 7:29 ` Rogier Wolff
2011-02-24 8:59 ` Amir Goldstein
2011-02-24 9:02 ` Rogier Wolff
2011-02-24 9:33 ` Amir Goldstein
2011-02-24 23:53 ` Rogier Wolff
2011-02-25 0:26 ` Daniel Taylor
2011-02-23 2:54 ` Rogier Wolff
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110220170931.GB3017@thunk.org \
--to=tytso@mit.edu \
--cc=R.E.Wolff@BitWizard.nl \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).