From: Denis Vlasenko <vda@ilport.com.ua>
To: Hans Reiser <reiser@namesys.com>
Cc: Chris Mason <mason@suse.com>,
linux-kernel@vger.kernel.org,
Reiserfs developers mail-list <Reiserfs-Dev@namesys.com>
Subject: Re: Recursive chmod/chown OOM kills box with 32MB RAM
Date: Mon, 30 Jan 2006 14:28:50 +0200 [thread overview]
Message-ID: <200601301428.50220.vda@ilport.com.ua> (raw)
In-Reply-To: <43DDAE2D.6080300@namesys.com>
On Monday 30 January 2006 08:11, Hans Reiser wrote:
> Denis Vlasenko wrote:
>
> >[CCing namesys]
> >
> >Narrowed it down to 100% reproducible case:
> >
> > chown -Rc 0:<n> .
> >
> >in a top directory of tree containing ~21938 files
> >on reiser3 partition:
> >
> > /dev/sdc3 on /.3 type reiserfs (rw,noatime)
> >
> >causes oom kill storm. "ls -lR", "find ." etc work fine.
> >
> >I suspected that it is a leak in winbindd libnss module,
> >but chown does not seem to grow larger in top, and also
> >running it under softlimit -m 400000 still causes oom kills
(typo, must be -m 40000000)
> >while chown's RSS stays below 4MB.
>
> Chris, would you like to handle this?
fs seems to be ok fsck-wise:
# mount -o remount,ro /.3
# reiserfsck /dev/sdc3
reiserfsck 3.6.11 (2003 www.namesys.com)
*************************************************************
** If you are using the latest reiserfsprogs and it fails **
** please email bug reports to reiserfs-list@namesys.com, **
** providing as much information as possible -- your **
** hardware, kernel, patches, settings, all reiserfsck **
** messages (including version), the reiserfsck logfile, **
** check the syslog file for any related information. **
** If you would like advice on using this program, support **
** is available for $25 at www.namesys.com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/sdc3
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Mon Jan 30 14:11:15 2006
###########
Filesystem seems mounted read-only. Skipping journal replay.
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
Leaves 8075
Internal nodes 52
Directories 1792
Other files 31865
Data block pointers 1058363 (0 of them are zero)
Safe links 0
###########
reiserfsck finished at Mon Jan 30 14:13:28 2006
###########
However, there is one strange thing: I cannot umount it.
Why? There is no open files.
# umount /.3
umount: /.3: device is busy
# lsof -nP | grep -F '/.3'
# lsof -nP | grep -F 'sdc'
# uname -a
Linux pegasus 2.6.14.6 #1 SMP Mon Jan 30 08:46:20 EET 2006 i686 unknown unknown GNU/Linux
--
vda
next prev parent reply other threads:[~2006-01-30 15:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 14:13 Denis Vlasenko
2006-01-28 15:01 ` Denis Vlasenko
2006-01-28 16:11 ` Denis Vlasenko
2006-01-30 6:11 ` Hans Reiser
2006-01-30 12:28 ` Denis Vlasenko [this message]
2006-02-01 15:21 ` Bernd Eckenfels
2006-02-03 6:21 ` Denis Vlasenko
2006-01-30 13:22 ` Chris Mason
2006-01-21 23:20 ` Pavel Machek
2006-02-02 15:17 ` Denis Vlasenko
2006-02-02 19:34 ` Bill Davidsen
2006-02-01 7:32 ` Denis Vlasenko
2006-02-01 7:42 ` Hans Reiser
2006-02-02 19:26 ` Bill Davidsen
2006-02-01 7:42 ` Denis Vlasenko
2006-02-01 10:15 ` Denis Vlasenko
2006-02-01 11:45 ` Vitaly Fertman
2006-02-01 14:25 ` Denis Vlasenko
2006-02-01 14:59 ` Denis Vlasenko
2006-02-01 11:52 ` Edward Shishkin
2006-02-01 14:26 ` Denis Vlasenko
2006-02-01 14:57 ` Denis Vlasenko
2006-02-01 15:14 ` Bernd Eckenfels
2006-02-01 15:28 ` Denis Vlasenko
2006-02-02 7:25 ` Denis Vlasenko
2006-02-02 9:42 ` Vitaly Fertman
2006-02-02 11:52 ` Denis Vlasenko
2006-02-02 19:32 ` Bill Davidsen
2006-02-03 5:57 ` Denis Vlasenko
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=200601301428.50220.vda@ilport.com.ua \
--to=vda@ilport.com.ua \
--cc=Reiserfs-Dev@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@suse.com \
--cc=reiser@namesys.com \
/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
Powered by JetHome