Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030366AbWBAKQr (ORCPT ); Wed, 1 Feb 2006 05:16:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030368AbWBAKQr (ORCPT ); Wed, 1 Feb 2006 05:16:47 -0500 Received: from 167.imtp.Ilyichevsk.Odessa.UA ([195.66.192.167]:34219 "HELO ilport.com.ua") by vger.kernel.org with SMTP id S1030366AbWBAKQq (ORCPT ); Wed, 1 Feb 2006 05:16:46 -0500 From: Denis Vlasenko To: Chris Mason Subject: Re: Recursive chmod/chown OOM kills box with 32MB RAM Date: Wed, 1 Feb 2006 12:15:54 +0200 User-Agent: KMail/1.8.2 Cc: Hans Reiser , linux-kernel@vger.kernel.org, Reiserfs developers mail-list References: <200601281613.16199.vda@ilport.com.ua> <200601300822.47821.mason@suse.com> <200602010942.36134.vda@ilport.com.ua> In-Reply-To: <200602010942.36134.vda@ilport.com.ua> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200602011215.54637.vda@ilport.com.ua> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 5324 Lines: 151 On Wednesday 01 February 2006 09:42, Denis Vlasenko wrote: > 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 > # 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' Removed it from /etc/fstab, after reboot: # reiserfstune -s 1024 /dev/sdc3 reiserfstune: Journal device has not been specified. Assuming journal is on the main device (/dev/sdc3). Current parameters: Filesystem state: consistent Reiserfs super block in block 16 on 0x823 of format 3.6 with standard journal Count of blocks on the device: 2094474 Number of bitmaps: 64 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 1019710 Root block: 32941 Filesystem is cleanly umounted Tree height: 4 Hash function used to sort names: "r5" Objectid map size 54, max 972 Journal parameters: Device [0x0] Magic [0x2cac04df] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 Blocks reserved by journal: 0 Fs state field: 0x0: sb_version: 2 inode generation number: 293892 UUID: 7b3aa1ab-40bd-44da-98dc-b37b21f7add0 LABEL: Set flags in SB: ATTRIBUTES CLEAN reiserfstune: Current journal parameters: Device [0x0] Magic [0x2cac04df] Size 8193 blocks (including 1 for journal header) (first block 18) Max transaction length 1024 blocks Max batch size 900 blocks Max commit age 30 WARNING: wrong transaction max size (1024). Changed to 511 reiserfstune: New journal parameters: Device [0x0] Magic [0x70dbc903] Size 1024 blocks (including 1 for journal header) (first block 18) Max transaction length 511 blocks Max batch size 449 blocks Max commit age 30 Reiserfs super block in block 16 on 0x823 of format 3.6 with non-standard journal Count of blocks on the device: 2094474 Number of bitmaps: 64 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 1019710 Root block: 32941 Filesystem is cleanly umounted Tree height: 4 Hash function used to sort names: "r5" Objectid map size 54, max 972 Journal parameters: Device [0x0] Magic [0x70dbc903] Size 1024 blocks (including 1 for journal header) (first block 18) Max transaction length 511 blocks Max batch size 449 blocks Max commit age 30 Blocks reserved by journal: 8193 Fs state field: 0x0: sb_version: 2 inode generation number: 293892 UUID: 7b3aa1ab-40bd-44da-98dc-b37b21f7add0 LABEL: Set flags in SB: ATTRIBUTES CLEAN reiserfstune: ATTENTION: YOU ARE ABOUT TO SETUP THE NEW JOURNAL FOR THE "/dev/sdc3"! AREA OF "/dev/sdc3" DEDICATED FOR JOURNAL WILL BE ZEROED! Continue (y/n):y Initializing journal - 0%....20%....40%....60%....80%....100% Syncing..ok # mount /dev/sdc3 /.3 -o noatime mount: you must specify the filesystem type # dmesg | tail -4 br: topology change detected, propagating br: port 1(ifi) entering forwarding state FAT: bogus number of reserved sectors VFS: Can't find a valid FAT filesystem on dev sdc3. # 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 Failed to open the journal device ((null)). Wow... 8( -- vda - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/