Re: reiserfsprogs 3.6.5-pre2 release.
>>># time reiserfsck -a /dev/sdb1 >>>Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal >>>Blocks (total/free): 143109020/59148009 by 4096 bytes >>>Filesystem is cleanly umounted >>>Replaying journal.. >>>0 transactions replayed >>>Checking internal tree..finished >>>real0m47.890s >>>user0m6.668s >>>sys 0m0.732s >>> >>> >> >>Thanks for trying. >>48 seconds is much longer than we expected such test should take. >>Was the system loaded at the time of test? >> > Yes, 48 seconds is too long to be acceptable. Would it be possible to lower the time it takes to mount a filesystem? Currently it takes about 48s to mount my fs: time mount /dev/Server/FTPRoot /glftpd/site -o noatime real0m48.906s user0m0.000s sys 0m0.090s FilesystemSize Used Avail Use% Mounted on /dev/Server/FTPRoot 744G 723G 21G 98% /glftpd/site ~ Anders
Re: reiserfsprogs 3.6.5-pre2 release.
Oleg Drokin wrote: Hello! On Wed, Feb 26, 2003 at 01:54:48AM +0100, Philippe Gramoull? wrote: # time reiserfsck -a /dev/sdb1 Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal Blocks (total/free): 143109020/59148009 by 4096 bytes Filesystem is cleanly umounted Replaying journal.. 0 transactions replayed Checking internal tree..finished real0m47.890s user0m6.668s sys 0m0.732s Thanks for trying. 48 seconds is much longer than we expected such test should take. Was the system loaded at the time of test? Bye, Oleg Yes, 48 seconds is too long to be acceptable. -- Hans
Re: reiserfsprogs 3.6.5-pre2 release.
Hi, On Wed, 26 Feb 2003 10:29:34 +0300 Oleg Drokin <[EMAIL PROTECTED]> wrote: | Hello! | | On Wed, Feb 26, 2003 at 01:54:48AM +0100, Philippe Gramoull? wrote: | > # time reiserfsck -a /dev/sdb1 | > Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal | > Blocks (total/free): 143109020/59148009 by 4096 bytes | > Filesystem is cleanly umounted | > Replaying journal.. | > 0 transactions replayed | > Checking internal tree..finished | > real0m47.890s | > user0m6.668s | > sys 0m0.732s | | Thanks for trying. | 48 seconds is much longer than we expected such test should take. | Was the system loaded at the time of test? The system was idle, doing absolutely nothing. Thanks, Philippe
Re: reiserfsprogs 3.6.5-pre2 release.
Hello! On Wed, Feb 26, 2003 at 01:54:48AM +0100, Philippe Gramoull? wrote: > # time reiserfsck -a /dev/sdb1 > Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal > Blocks (total/free): 143109020/59148009 by 4096 bytes > Filesystem is cleanly umounted > Replaying journal.. > 0 transactions replayed > Checking internal tree..finished > real0m47.890s > user0m6.668s > sys 0m0.732s Thanks for trying. 48 seconds is much longer than we expected such test should take. Was the system loaded at the time of test? Bye, Oleg
Re: reiserfsprogs 3.6.5-pre2 release.
Hi Vitaly, here is an output of reiserfsck -a on a ~550 Gb Raid5 array filled about 60%. # df /dev/sdb1 Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdb1572418604 335826568 236592036 59% /prod # reiserfsck -V <-reiserfsck, 2002-> reiserfsprogs 3.6.5-pre2 # time reiserfsck -a /dev/sdb1 Reiserfs super block in block 16 on 0x811 of format 3.6 with standard journal Blocks (total/free): 143109020/59148009 by 4096 bytes Filesystem is cleanly umounted Replaying journal.. 0 transactions replayed Checking internal tree..finished real0m47.890s user0m6.668s sys 0m0.732s Hope that helps. Thanks, Philippe On Tue, 25 Feb 2003 17:12:45 +0300 Vitaly Fertman <[EMAIL PROTECTED]> wrote: | Also, it would be interesting to know how much time does reiserfsck -a take | on big arrays. So if you have a such, try it also please. I mean, on consistent | filsystems, otherwise reiserfsck will switch to the fix-fixable mode. -- Philippe Gramoullé [EMAIL PROTECTED] Lycos Europe - NOC France
Re: reiserfsprogs 3.6.5-pre2 release.
On Tuesday 25 February 2003 19:25, [EMAIL PROTECTED] wrote: > Vitaly, how does "check-followed-by-fixable" in 3.6.3 compare to > "-a" at boot in 3.6.5? First, 3.6.3 is quite old version and many bugs were fixed since then, you should update it. When you run reiserfsck-3.6.5-pre2 -a, it does a few light-weight checks - check some fields in the super block, replay the journal, bitmap, if the last block of the fs is readable, and just 2 upper levels of internal tree are checked. It is supposed to take not more then a few seconds. reiserfsck in check mode goes through the whole internal tree, not just 2 levels, checking nodes structure and links between them, and then (if there is no fatal corruptions) does semantic check - goes through the whole tree of directories checking them and checking all files. This takes more time. -- Thanks, Vitaly Fertman
RE: reiserfsprogs 3.6.5-pre2 release.
Vitaly, how does "check-followed-by-fixable" in 3.6.3 compare to "-a" at boot in 3.6.5? Regards, Wayne. -Original Message- From: Vitaly Fertman [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 25, 2003 8:50 AM To: [EMAIL PROTECTED] Subject: reiserfsprogs 3.6.5-pre2 release. Hi all! this new pre-release includes: - a critical bug on pass0 of rebuild-tree with overflowing while checking unformatted item offsets was fixed. - a bug in relocation of shared object id - entry key sometimes does not get updated correctly with the new key - was fixed. - a bug in bitops operations for be mashins was fixed. - a bug with the superblock overwriting during replaying was fixed. - while openning the journal check that journal parameters in the superblock and in the journal header mathches; advice to run rebuild-sb if not. While rebuilding the superblock, do the same check and ask the user if he wants to rebuild the journal header or continue w/out the journal or he wants to change the start of the partition before using reiserfsck. - check that all not valid bits of the bitmap are set to 1, set it correctly. - fix-fixable does not relocate shared object ids anymore, as it is too complex for fix-fixable and only rebuild-tree does. - reiserfsck -a (started at boot) replays journal, checks error flags in the superblock, bitmaps, fs size, 2 levels of internal tree and switches to fixble mode if any problem is detected. For root fs fixable cannot be performed (as fs is mounted) and just --check will be done. - Journal replay was improved a) check blocks if they could be journable before replaying; b) replay only transactions which has trans_id == last replayed transaction trans_id + 1. - warning messages were improved. -- Thanks, Vitaly Fertman
Re: reiserfsprogs 3.6.5-pre2 release.
On Tuesday 25 February 2003 16:50, Vitaly Fertman wrote: > Hi all! > > - a critical bug on pass0 of rebuild-tree with overflowing while checking > unformatted item offsets was fixed. > > - reiserfsck -a (started at boot) replays journal, checks error flags in > the superblock, bitmaps, fs size, 2 levels of internal tree and switches > to fixble mode if any problem is detected. For root fs fixable cannot be > performed (as fs is mounted) and just --check will be done. As the pre release has one critical bug fixed and we would like to make it a new release as soon as possible, any test of how rebuild-tree works on filesystems with big files is appreciated. Also, it would be interesting to know how much time does reiserfsck -a take on big arrays. So if you have a such, try it also please. I mean, on consistent filsystems, otherwise reiserfsck will switch to the fix-fixable mode. -- Thanks, Vitaly Fertman
