From: Denis Vlasenko <vda@ilport.com.ua>
To: Chris Mason <mason@suse.com>
Cc: Hans Reiser <reiser@namesys.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: Wed, 1 Feb 2006 09:42:36 +0200 [thread overview]
Message-ID: <200602010942.36134.vda@ilport.com.ua> (raw)
In-Reply-To: <200601300822.47821.mason@suse.com>
On Monday 30 January 2006 15:22, Chris Mason wrote:
> You can shrink the log of an existing filesystem. The minimum size is 513
> blocks, you might try 1024 as a good starting poing.
>
> reiserfstune -s 1024 /dev/xxxx
>
> The filesystem must be unmounted first.
It doesn't want to, for no obvious reason:
# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (ro,nogrpid)
none on /proc type proc (rw,nodiratime)
none on /sys type sysfs (rw)
none on /dev type ramfs (rw)
/dev/sda2 on /.share type ext2 (rw,noatime,nogrpid)
/dev/sdb2 on /.1 type reiserfs (rw,noatime)
/dev/sdc2 on /.2 type reiserfs (rw,noatime)
/dev/sdc3 on /.3 type reiserfs (rw,noatime)
/dev/sda2 on /.local type ext2 (rw,noatime,nogrpid)
none on /dev/pts type devpts (rw)
automount(pid1043) on /.local/mnt/auto type autofs (rw)
# umount /.3
umount: /.3: device is busy
# mount -o ro,remount /.3
# umount /.3
umount: /.3: device is busy
# mount
rootfs on / type rootfs (rw)
/dev/root on / type ext2 (ro,nogrpid)
none on /proc type proc (rw,nodiratime)
none on /sys type sysfs (rw)
none on /dev type ramfs (rw)
/dev/sda2 on /.share type ext2 (rw,noatime,nogrpid)
/dev/sdb2 on /.1 type reiserfs (rw,noatime)
/dev/sdc2 on /.2 type reiserfs (rw,noatime)
/dev/sdc3 on /.3 type reiserfs (ro,noatime)
/dev/sda2 on /.local type ext2 (rw,noatime,nogrpid)
none on /dev/pts type devpts (rw)
automount(pid1043) on /.local/mnt/auto type autofs (rw)
# reiserfstune /dev/sdc3
reiserfstune: Reiserfstune is not allowed to be run on mounted filesystem.
# lsof -nP | grep -F '/.3'
# lsof -nP | grep -F '/dev/sdc'
--
vda
next prev parent reply other threads:[~2006-02-01 7:43 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-28 14:13 Recursive chmod/chown OOM kills box with 32MB RAM 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
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 [this message]
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=200602010942.36134.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