Re: Reiser4 support on parted program ...
Hans Reiser wrote: Dr. Giovanni A. Orlando wrote: As soon the installer works fine supporting Reiser4, including parted support it, I will comment in this mailing list, and offer for free donwload. Reiser4 resizer is not ready for prime time, and like pseudos, should not have been enabled before it was tested. We are going to send in a patch to turn it off until it is debugged. hello Hans, I suspect, that Dr. Giovanni A. Orlando meant offline resizer which should be in utils. Not online resizer-repacker... -- umka
Re: Reiser4 support on parted program ...
Dr. Giovanni A. Orlando wrote: Yury Umanets wrote: Hans Reiser wrote: Dr. Giovanni A. Orlando wrote: As soon the installer works fine supporting Reiser4, including parted support it, I will comment in this mailing list, and offer for free donwload. Reiser4 resizer is not ready for prime time, and like pseudos, should not have been enabled before it was tested. We are going to send in a patch to turn it off until it is debugged. hello Hans, I suspect, that Dr. Giovanni A. Orlando meant offline resizer which should be in utils. Not online resizer-repacker... Actually, we want that reiser4 is supported inside parted program. Nothing else. I don't think this support will enable any other support like reiser4-resize. One of options provided by parted is offline resizing though... Thanks, Giovanni -- umka
Re: Gnu Parted error, Kernel Panic, Reiserfs
On Fri, 2004-04-16 at 17:06, Szakacsits Szabolcs wrote:
On Fri, 16 Apr 2004, Yury Umanets wrote:
One more thing. Is it common case, that resizier errors happen on Gento?
Hmmm, seems to be a good point. Alan had Gentoo. On the QTParted forums
people mention Gentoo. SystemRescueCD (http://www.sysresccd.org), the most
popular LiveCD for partition handling is Gentoo based ...
Look what I've found right now:
http://www.sysresccd.org/forums/viewtopic.php?t=294
Why is it that with and only with System Rescue CD, if I format a
partition as reiserfs, then copy some data from another resierfs
partition to that newly formatted partition and then unmount the
partition and run fsck on it, errors are found that need fixing?
Szaka
Hello all,
I have new progsreiserfs at:
http://o3test.iit.nau.edu.ua/pr/progsreiserfs-0.3.0.5.tar.gz
ftp://ftp.namesys.com/pub/libreiserfs/progsreiserfs-0.3.0.5.tar.gz
It has a function which can be used for simple tree check. Check is
sufficient to say, that if it pass, resizing will pass too if there is
no bad blocks on device.
Also see parted patch in attachment.
PS. Unfortunately I was not able to find gentoo source package of
progsreiserfs (is it exists? I'm not familiar with Gentoo) to check if
it is modified or not. So, if one can say me where I can take it, please
do. Thanks in advance.
Thanks.
--
umka
diff -rupN ./parted-1.6.10.orig/configure.in ./parted-1.6.10.check/configure.in
--- ./parted-1.6.10.orig/configure.in 2004-04-16 03:22:07.0 +0300
+++ ./parted-1.6.10.check/configure.in 2004-04-19 13:47:09.0 +0300
@@ -239,6 +239,9 @@ if test $enable_dynamic_loading = no -
REISER_LIBS=-ldal -lreiserfs
AC_DEFINE(HAVE_LIBREISERFS, 1, [Have libreiserfs])
)
+ AC_CHECK_LIB(reiserfs, reiserfs_fs_check,
+ AC_DEFINE(HAVE_REISERFS_FS_CHECK, 1, [Have reiserfs_fs_check()])
+ )
)
LIBS=$OLD_LIBS
fi
diff -rupN ./parted-1.6.10.orig/libparted/fs_reiserfs/reiserfs.c ./parted-1.6.10.check/libparted/fs_reiserfs/reiserfs.c
--- ./parted-1.6.10.orig/libparted/fs_reiserfs/reiserfs.c 2002-08-10 03:47:33.0 +0300
+++ ./parted-1.6.10.check/libparted/fs_reiserfs/reiserfs.c 2004-04-19 13:55:34.0 +0300
@@ -100,8 +100,11 @@ FCLASS reiserfs_fs_t* (FPTR reiserfs_fs_
reiserfs_gauge_t *);
FCLASS int (FPTR reiserfs_fs_resize) (reiserfs_fs_t *, blk_t, reiserfs_gauge_t *);
+FCLASS int (FPTR reiserfs_fs_check) (reiserfs_fs_t *, reiserfs_gauge_t *);
+
FCLASS reiserfs_fs_t *(FPTR reiserfs_fs_copy) (reiserfs_fs_t *, dal_t *,
reiserfs_gauge_t *);
+
FCLASS int (FPTR reiserfs_fs_clobber) (dal_t *);
FCLASS void (FPTR reiserfs_fs_close) (reiserfs_fs_t *);
@@ -383,6 +386,7 @@ static PedConstraint *reiserfs_get_creat
static int reiserfs_check(PedFileSystem *fs, PedTimer *timer)
{
reiserfs_fs_t *fs_info;
+ reiserfs_gauge_t *gauge = NULL;
PED_ASSERT(fs != NULL, return 0);
@@ -410,6 +414,34 @@ static int reiserfs_check(PedFileSystem
return 0;
}
+#ifdef HAVE_REISERFS_FS_CHECK
+ ped_timer_reset(timer);
+
+ if (libreiserfs_gauge_create libreiserfs_gauge_free) {
+ if (!
+ (gauge =
+ libreiserfs_gauge_create(NULL, gauge_handler, timer)))
+ return 0;
+ }
+
+ ped_timer_set_state_name(timer, _(checking));
+ ped_timer_update(timer, 0.0);
+
+ if (!reiserfs_fs_check(fs_info, gauge)) {
+ ped_exception_throw(PED_EXCEPTION_ERROR,
+PED_EXCEPTION_CANCEL,
+_
+(Reiserfs tree seems to be corrupted.
+ Run reiserfsck --check first.));
+ return 0;
+ }
+
+ ped_timer_update(timer, 1.0);
+
+ if (gauge)
+ libreiserfs_gauge_free(gauge);
+#endif
+
ped_exception_throw(PED_EXCEPTION_INFORMATION, PED_EXCEPTION_OK,
_
(The reiserfs filesystem passed a basic check. For a more
Re: labels and uuids setting/showing
Tobias Burnus wrote: Hi, Hello, I know that reiserfstune can set UUIDs and labels on a not-mounted reiser file system. But how can I (a) show the current UUID and label of a (mounted/not-mounted) reiser3? You can use debugreiserfs to show all the information you are interesed if a partition is not mounted. And how can I set the label and/or the UUID without u(n)mounting? reiserfstune currently complains that it cannot rebuild the tree on a mounted system. And if it is mounted, probably mount will show something usefull. Tobias -- umka
Re: Reiser4 input/output errors...
On Tue, 2003-09-02 at 20:51, Mike Benoit wrote: Since I enabled all the debugging options that would compile, I re-ran the mkfs.reiser4 /dev/hda8, then attempted to untar the linux kernel again, however it didn't like that very much: Here is what I got from the log: lookup inode: 65897 de4x5.c creating de4x5.c in 65897 reiser4 panicked cowardly: assertion failed: carry_level_invariant(doing, CARRY_DOING) Hopefully this is enough information to help you track down the problem. On Mon, 2003-09-01 at 22:03, Yury Umanets wrote: On Tue, 2003-09-02 at 01:53, Mike Benoit wrote: I assume this isn't supposed to happen? [EMAIL PROTECTED] home]# mkfs.reiser4 /dev/hda8 mkfs.reiser4 0.4.12 Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING. Information: Reiser4 is going to be created on /dev/hda8. (Yes/No): Yes Creating reiser4 on /dev/hda8...done Synchronizing /dev/hda8...done [EMAIL PROTECTED] home]# mount -t reiser4 /dev/hda8 /home/test2 [EMAIL PROTECTED] test2]# cd /home/test2 [EMAIL PROTECTED] test2]# cp /usr/src/linux-2.6.0-test4.tar.bz2 ./ [EMAIL PROTECTED] test2]# tar jxf linux-2.6.0-test4.tar.bz2 [EMAIL PROTECTED] test2]# rm -rf linux-2.6.0-test4/ rm: reading directory `linux-2.6.0-test4//drivers/net/e100': Input/output error rm: reading directory `linux-2.6.0-test4//drivers/net/sk98lin': Input/output error rm: cannot remove directory `linux-2.6.0-test4//drivers/net': Directory not empty I tried this on two different partitions (/dev/hda7 and /dev/hda8) the exact same files had the error on both, so it seems to be reproducible. It does however work fine if I use ext3 on the said partitions. This is a brand new HD (about a week old) so I doubt it has any bad blocks (badblocks /dev/hda8 doesn't report anything). [EMAIL PROTECTED] home]# mkfs.reiser4 --version mkfs.reiser4 0.4.12 Kernel: 2.6.0-test4 #5 Mon Sep 1 14:20:14 PDT 2003 i686 unknown unknown GNU/Linux CONFIG_REISER4_FS=y CONFIG_REISER4_LARGE_KEY=y CPU: cpu family : 6 model : 8 model name : AMD Athlon(tm) Processor stepping: 1 cpu MHz : 1662.612 cache size : 256 KB Distro: Mandrake 9.2beta. There is something interesting in kernel logs? Hello, Can you run debugfs.reiser4 on /dev/hda8? What does it say?
Re: small problem configuring and installing reiser4progs
On Wed, 2003-08-27 at 05:11, Tupshin Harper wrote: I just downloaded and installed reiser4progs-0.4.12 and libaal-0.4.9. This was the first install of either of these, and I ran into the following problem: configured and make installed libaal-0.4.9 configure of reiser4progs ends with the following: checking whether -falign-loops works... yes checking for aal_device_open in -laal... yes checking aal/aal.h usability... yes checking aal/aal.h presence... yes checking for aal/aal.h... yes checking for libaal version = 0.4.9... no It ends there, without any indication that there was a fatal error, but it didn't build the Makefiles. So, two problems...insufficient error reporting, as well as a slight problem with the process. After running ldconfig, configure works just fine. -Tupshin That is because your ldcache is still not updated. Run ldconfig under root first. Regards.
Re: reiser4 snapshot for August 26th.
On Wed, 2003-08-27 at 09:52, Ian Wienand wrote: On Tue, Aug 26, 2003 at 02:22:33PM +0400, Oleg Drokin wrote: Fixed some bugs. And finally reiser4 should compile on 64bit boxes (hm. somebody try it, as I am unable to build any 2.6 kernel for ia64). I built this with IA64 2.6.0-test4, it works but there were lots of warnings (I can put up a log if you want it). This was on a dual processor Itanium 2 box. First up, I tried a little test to make a few files, but once I had unmounted the disk I couldn't re-mount it. --- example testing below --- bash-2.05b# mkfs.reiser4 /dev/sda5 mkfs.reiser4 0.4.12 Copyright (C) 2001, 2002, 2003 by Hans Reiser, licensing governed by reiser4progs/COPYING. Information: Reiser4 is going to be created on /dev/sda5. (Yes/No): Yes Creating reiser4 on /dev/sda5... mkfs.reiser4(5676): unaligned access to 0x600242f2, ip=0x200f7661 mkfs.reiser4(5676): unaligned access to 0x600242fa, ip=0x200f77a1 mkfs.reiser4(5676): unaligned access to 0x60024302, ip=0x200f78e1 mkfs.reiser4(5676): unaligned access to 0x600242f2, ip=0x200f2671 done Synchronizing /dev/sda5...done I will fix it soon. Thanks for report. Regards.
Re: reiser4 snapshot
On Tue, 2003-08-12 at 11:22, Cyrille Chepelov wrote: Le Tue, Aug 12, 2003, à 10:05:42AM +0400, Oleg Drokin a écrit: Hello! Hello, On Mon, Aug 11, 2003 at 05:32:25PM -0700, Boris Tschirschwitz wrote: I thought I'd give it a try on 2.6.0-test3-mm1. Even with 'make mrproper' before compiling, I get the following error message: (Is there any interest in such error reports?) Yes, there is. I have a problem: reiserfs4progs doesn't seem to pay attention to the --prefix when it comes to locating libaal. --prefix is not the prefix libraries are looked at. It is the prefix of where package libraries and includes will be installed. I configured libaal with --prefix=/scratch/riesling/reiser4-inst and installed it there, then tried to configure reiserfs4progs with the same prefix, and it still fails to locate libaal. You need to let dynamic linker know, that some interesting libraries lie at some location. Edit /etc/ld.so.conf and there line /scratch/riesling/reiser4-inst Or set evn. variable LD_LIBRARY_PATH like the following: export LD_LIBRARY_PATH=/scratch/riesling/reiser4-inst:$LD_LIBRARY_PATH When I force it a little by prepending the call to ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal, but chokes on locating aal/aal.h. This will be fixed. Thanks. temporary cure is to specify CFLAGS durring make: make CFLAGS=-I/scratch/riesling/reiser4-inst/include/aal I'll sure get past that, but it's a little annoying, and might get in the way of distributors (depending on the way they package libaal, ie separately or merged with the main reiserfs4progs package). libaal is planed to be used with another similar projects to as it contains useful utilities like device abstraction, etc. So, it is better to have it as separated package. But reiser4progs building may be automated. -- Cyrille -- We're flying high, we're watching the world passes by...
Re: Reiser4 status: benchmarked vs. V3 (and ext3)
On Thu, 2003-08-14 at 00:12, Bill Davidsen wrote: On Sun, 27 Jul 2003, Yury Umanets wrote: On Sun, 2003-07-27 at 18:10, Daniel Egger wrote: Am Son, 2003-07-27 um 15.28 schrieb Hans Reiser: or for which a wear leveling block device driver is used (I don't know if one exists for Linux). This is normally done by the filesystem (e.g. JFFS2). Normally device driver should be concerned about making wear out smaller. It is up to it IMHO. The driver should do the logical to physical mapping, but the portability vanishes if the filesystem to physical mapping is not the same for all machines and operating systems. For pluggable devices this is important. The leveling seems to be done by JFFs2 in a portable way, and that's as it should be. If the leveling were in the driver I don't believe even FAT would work. Hello Bill, Yes, you are right. Device driver cannot take care about leveling. It is able only to take care about simple caching (one erase block) in order to make wear out smaller and do not read/write whole block if one sector should be written. Part of a filesystem called block allocator should take care about leveling.
Re: reiser4 snapshot
On Tue, 2003-08-12 at 12:02, Cyrille Chepelov wrote: Le Tue, Aug 12, 2003, à 11:31:57AM +0400, Yury Umanets a écrit: I have a problem: reiserfs4progs doesn't seem to pay attention to the --prefix when it comes to locating libaal. --prefix is not the prefix libraries are looked at. It is the prefix of where package libraries and includes will be installed. yes, of course. However, you saw that it's not the only problem. When I force it a little by prepending the call to ./configure with suitable CFLAGS and LDFLAGS, it goes past locating libaal, but chokes on locating aal/aal.h. This will be fixed. Thanks. temporary cure is to specify CFLAGS durring make: make CFLAGS=-I/scratch/riesling/reiser4-inst/include/aal can't be done, as there is no Makefile until configure completes -- and it can't complete as it doesnt pay attention to things like CFLAGS=-I/.../include ./configure I got past that, though. Another little glitch is that the configure.in explicitly checks for 0.4.8 while the provided libaal is 0.4.9. No biggie, just requires modifying the configure.in and re-running autoconf (you might want to add a check against that condition in your pre-upload QA scripts). Hello, Everything is fixed and new snapshot is in http://thebsh.namesys.com/snapshots/2003.08.11/. See ./configure --help for new option --with-libaal. Thanks for reports one more time.
Re: reiser4 snapshot
On Tue, 2003-08-12 at 13:48, Cyrille Chepelov wrote: Le Tue, Aug 12, 2003, à 12:25:58PM +0400, Yury Umanets a écrit: Everything is fixed and new snapshot is in http://thebsh.namesys.com/snapshots/2003.08.11/. See ./configure --help for new option --with-libaal. That fixes it, thanks! It can be debated whether --with-libaal=/foo/bar should imply LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/foo/bar/lib or not (it doesn't seem it does right now), but at least it's now possible to build and install libaal + reiser4progs in a user tree without touching /usr. I guess, it is not the job for configure script, but rather for user/administrator. At least I don't even one project that do so :) -- Cyrille
Just to mention...
Hello all, I just want to let our developers and testers know, that mkfs and another reiser4 utility programs has changed their options recently. So, it is probably needed to update benchmarks, scripts, etc. For instance, to create reiser4 with short keys you need to type something like this: mkfs.reiser4 -qf /dev/test_device -o key=key_short and to create reiser4 with particular tail policy you need to type the following: mkfs.reiser4 -qf /dev/test_device -o policy=(tails|extents|smart) To list all available plugins and current profile use mkfs.reiser4 -p and mkfs.reiser4 -P correspondingly. See corresponding manual pages for details. Happy testing. Regards.
Re: ReiserFS on a flash device?
On Mon, 2003-07-28 at 11:05, Shawn Rutledge wrote: On Mon, Jul 28, 2003 at 08:53:57AM +0400, Yury Umanets wrote: On Mon, 2003-07-28 at 06:33, Mike Fedyk wrote: On Sun, Jul 27, 2003 at 02:55:31PM +0400, Yury Umanets wrote: Default journal size is too big (32MB) for usual embedded device. I mean, that flash is expensive and it is pity to loss 32MB for journal :) What? You mean it isn't reduced in size based on block device size like with ext3? Yes, is isn't. Use reiserfstune to make it smaller. Well I'm glad to hear it's possible to use ReiserFS on small devices, but I think that requiring a kernel patch, or a GRUB patch, to handle different journal sizes is not good. Are there plans to have the kernel and GRUB detect it at runtime? Support for non-standard journal is merged to kernel recently. Use last pre or wait until next stable kernel is released. GRUB is able to with with it too. Use ftp://ftp.namesys.com/pub/misc-patches/grub-0.93-reiserfs-non-standard-journal.diff for that. Regards. -- We're flying high, we're watching the world passes by...
Re: ReiserFS on a flash device?
On Mon, 2003-07-28 at 06:33, Mike Fedyk wrote: On Sun, Jul 27, 2003 at 02:55:31PM +0400, Yury Umanets wrote: Default journal size is too big (32MB) for usual embedded device. I mean, that flash is expensive and it is pity to loss 32MB for journal :) What? You mean it isn't reduced in size based on block device size like with ext3? Yes, is isn't. Use reiserfstune to make it smaller. IIRC, it defaults to 2-4MB on a 100MB device. -- We're flying high, we're watching the world passes by...
Re: Mapping reiserfs errors to hardware devices or filesystems
On Mon, 2003-07-28 at 09:01, Donald Thompson wrote: I believe I'm having a hardware issue, but I have no idea what device is the problem from the error messages I'm getting. I'm seeing the following repeated: vs-500: unknown uniqueness 26169 vs-500: unknown uniqueness 26169 vs-500: unknown uniqueness 26169 vs-500: unknown uniqueness 26169 vs-500: unknown uniqueness 26169 vs-500: unknown uniqueness 26169 vs-5150: search_by_key: invalid format found in block 90922. Fsck? vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [26164 26256 0x0 SD] Its been repeating itself over several reboots. It does not seem to be fatal, as the system remains up and working properly. The entire system, including the root device uses reiserfs. 4 of the filesystems sit on logical volumes. This is a debian sid system, kernel 2.4.20. Is there any way from the messages generated to identify what filesystem is having problems? I figure my only other option is to go into single user mode, mount everything read-only and fsck each filesystem. I'm just lazy and was hoping there was an easier way of tracking it down. Any help is much appreciated. Hello, This is fixed in last pre kernels. -Don -- We're flying high, we're watching the world passes by...
Re: Patch for 2.6.0-test1 kernel
On Thu, 2003-07-17 at 23:48, Michael Konrad wrote: Hello, Not yet, but we're considering about. Is there a reiser4 patch for the 2.6.0-test1 kernel? Thank you. -Michael -- We're flying high, we're watching the world passes by...
Re: I go to America on Sunday, back around April 24th, will probablybe hard to reach by email during much of that time period
Hans Reiser wrote: I should be flying into DC right at around the time when some people are guessing will be the start of the war, hopefully I won't hit anything.;-) I'm sure you will fine :) -- Yury Umanets
Re: cannot mount /dev/hdc1
Ingo Rößler wrote: Hello, I hope You can help me! I get at the reboot of my Suse7.1-Linux-server this message: mount -t reiserfs /dev/hdc1 /home : mount: wrong fs type, bad option, bad superblock on /dev/hdc1, or too many mounted file systems This is my home-directory - my live! The harddisk is correct connected. It is a Western Digial 80 GB Harddisk with only this Partition hdc1. elsa:~ # cat /etc/fstab /dev/hda1 /windowsvfatdefaults0 0 /dev/hda2 swapswappri=42 0 0 /dev/hda3 / reiserfsdefaults1 1 /dev/hdc1 /home reiserfsdefaults1 2 /dev/hda5 /home/backup reiserfsdefaults 1 2 /dev/cdrom /home/mount/cdrom autoro,noauto,user,exec 0 0 /dev/dvd/home/mount/dvd autoro,noauto,user,exec 0 0 /dev/fd0/home/mount/floppy autonoauto,user,sync 0 0 proc/proc procdefaults0 0 devpts /dev/ptsdevpts defaults0 0 elsa:~ # reiserfsck --check /dev/hdc1 -reiserfsck, 2001- reiserfsprogs 3.x.0j reiserfs_open: neither new nor old reiserfs format found on /dev/hdc1 reiserfsck: --rebuild-sb may restore reiserfs super block Now I boot with a newer OS: Knoppix, a CDROM-Linux-Distri: mount -t reiserfs /dev/hdc1 /mnt read_super_block: can't find a reiserfs filesystem on (dev 16:01, block 128, size 512) read_super_block: can't find a reiserfs filesystem on (dev 16:01, block 16, size 512) mount : Falscher Dateisystemtyp, ungültige Optionen, der Superblock von /dev/hdc1 ist beschädigt oder es sind zu viele Dateisysteme eingehängt. # reiserfsck --check /dev/hdc1 -reiserfsck, 2002- reiserfsprogs 3.6.3 reiserfs_open: neither new nor old reiserfs format found on /dev/hdc1 reiserfsck: could not open filesystem on /dev/hdc1 Aborted What can I do? Can you help me? Ciao Ingo PS: Excuse my bad english. Excuse my using of OE - my Netscape is on /home/ Well, you might try to rebuild super block. Backup your data first if it possible and run: reiserfsck --rebuild-sb /dev/hdc1 What does it say? Try also this command: dd if=/dev/hdc1 of=/tmp/super bs=4096 count=1 skip=16 and send us /tmp/super file please.
Re: reiserfsck --no-journal-available --do-as-i-fucking-say-bitch
[EMAIL PROTECTED] wrote: Hi there, I have a reiserfs filesystem that has a corrupted journal; whenever I try to mount it, fsck it (including with the --no-journal-available option), etc reiserfs tries to seek beyond the end of the block device. Is there an easy way to blank the journal so that I can run reiserfsck on it? (none):/mnt/backups# reiserfsck /dev/hda1 -reiserfsck, 2002- reiserfsprogs 3.x.1b Will read-only check consistency of the filesystem on /dev/hda1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes):Yes ### reiserfsck --check started at Fri Feb 7 10:43:10 2003 ### Replaying journal.. trans replayed: mountid 101, transid 216560, desc 6118, len 72, commit 6191, nex t trans offset 6174 bwrite: lseek to position 2048503808 (block=500123, dev=4): Invalid argument (none):/mnt/backups# reiserfsck --no-journal-available /dev/hda1 -reiserfsck, 2002- reiserfsprogs 3.x.1b Will read-only check consistency of the filesystem on /dev/hda1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes):Yes Filesystem with standard journal found, --no-journal-availabel is ignored ### reiserfsck --check started at Fri Feb 7 10:43:29 2003 ### Replaying journal.. trans replayed: mountid 101, transid 216560, desc 6118, len 72, commit 6191, nex t trans offset 6174 bwrite: lseek to position 2048503808 (block=500123, dev=4): Invalid argument (none):/mnt/backups# Here is what I get on the console when I try to mount: mount: wrong fs type, bad option, bad superblock on /dev/hda1, or too many mounted file systems Replay Failure, unable to mount reiserfs_read_super: unable to initialize journal space reiserfs: checking transaction log (device 03:01) ... attempt to access beyond end of device 03:01: rw=1, want=2000496, limit=261 attempt to access beyond end of device 03:01: rw=1, want=2000500, limit=261 journal-1226: REPLAY FAILURE, fsck required! buffer write failed Replay Failure, unable to mount reiserfs_read_super: unable to initialize journal space Here's the output of debugreiserfs -j (I think - the journal header option) Filesystem state: consistency is not checked after last mounting Reiserfs super block in block 16 on 0x301 of format 3.6 with standard journal Count of blocks on the device: 524112 Number of bitmaps: 16 Blocksize: 4096 Free blocks (count of blocks - used [journal, bitmaps, data, reserved] blocks): 60981 Root block: 37661 Filesystem is NOT cleanly umounted Tree height: 5 Hash function used to sort names: r5 Objectid map size 2, max 972 Journal parameters: Device [0x0] Magic [0x2d5b5922] 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: 214154 UUID: cbf04f8b-8d1c-4f07-813e-e449c393c294 LABEL: Set flags in SB: ATTRIBUTES CLEAN Journal header (block #8210 of /dev/hda1): j_last_flush_trans_id 216559 j_first_unflushed_offset 6100 j_mount_id 101 Device [0x0] Magic [0x2d5b5922] 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 Is there an easy override for this? Why is the option there, if it is ignored in the standard case? Cheers, Sam. Please download recent version of reiserfsprogs at ftp://ftp.namesys.com/pub/reiserfsprogs/pre/reiserfsprogs-3.6.5-pre1.tar.gz and try one more time. Let us know what does it say.
Re: build problem BK reiser4progs: /usr/include/features.h:218:52:operator '==' has no left operand
Ookhoi wrote: Yury Umanets wrote (ao): No, it is not nornal case. It is pretty strange. Try the fllowing sequence: bk pull aclocall autoheader aitomake --add-missing autoconf ./configure make distclean ./configure make make install ldconfig -v | grep reiser4 And let's see what happen # ldconfig -v | grep reiser4 # Empty (after fresh pull). I can provide the output of all the above commands if you like (it's a bit large). Would that help you? Yes, of course. Send me the all build output as a tar.gz Oki, attached. Had to do it again as the first capture failed. Looks like the problem is in line gcc -g -O2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -g -W -Wall -Wno-unused -Werror -DPLUGIN_DIR=\/usr/l ocal/lib/reiser4\ -o debugfs.reiser4 debugfs.o ../../libreiser4/.libs/libreiser4.a ../../progs/lib misc/.libs/libmisc.a /usr/src/reiser4progs/libaal/.libs/libaal.a -lncurses -lreadline Your libtool has decided to link all binaries against static library ../../libreiser4/.libs/libreiser4.a. This library contains plugins code too. But, lnker was unable to find direct links to plugin symbols. That is because they do not exist, we're working with plugins by means of using interface structs for example, item_ops, which contains all methods of corresponding item plugin. So, linker did not include plugin symbols into result binary. The cure ptobably is to install more recent libtool. -- Yury Umanets
Re: build problem BK reiser4progs: /usr/include/features.h:218:52:operator '==' has no left operand
Ookhoi wrote: Yury Umanets wrote (ao): Looks like the problem is in line gcc -g -O2 -D_REENTRANT -D_FILE_OFFSET_BITS=64 -g -W -Wall -Wno-unused -Werror -DPLUGIN_DIR=\/usr/l ocal/lib/reiser4\ -o debugfs.reiser4 debugfs.o ../../libreiser4/.libs/libreiser4.a ../../progs/lib misc/.libs/libmisc.a /usr/src/reiser4progs/libaal/.libs/libaal.a -lncurses -lreadline Your libtool has decided to link all binaries against static library ../../libreiser4/.libs/libreiser4.a. This library contains plugins code too. But, lnker was unable to find direct links to plugin symbols. That is because they do not exist, we're working with plugins by means of using interface structs for example, item_ops, which contains all methods of corresponding item plugin. So, linker did not include plugin symbols into result binary. The cure ptobably is to install more recent libtool. Oke, I'll search for a more recent one. I do run an up to date debian sid (unstable) though. Hm :-) ookhoi $ libtool --version ltmain.sh (GNU libtool) 1.4.3 (1.922.2.111 2002/10/23 02:54:36) libtool --version ltmain.sh (GNU libtool) 1.4.2 (1.922.2.53 2001/09/11 03:18:52) I'll report success or failure. Thanks! Thanks to you :) I'll find the cure :) -- Yury Umanets
Re: Core dump in reiserfsck
Vitaly Porotikov wrote: Folks, Perhaps 3.x1c have not this bug, but I can't do any changes in my system. I send it in hope to find some coding errors out (if this wasn't before). [root@tkprzbkup5 /root]# mount /dev/rza1 on / type ext2 (rw) none on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) /dev/rze1 on /export type reiserfs (ro) [root@tkprzbkup5 /root]# reiserfsck --check /dev/rze1 -reiserfsck, 2002- reiserfsprogs 3.x.1b Will read-only check consistency of the filesystem on /dev/rze1 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes):Yes ### reiserfsck --check started at Wed Jan 15 10:41:40 2003 ### Filesystem seems mounted read-only. Skipping journal replay.. Checking S+tree../ 72 (of 98)/101 (of 153)/124 (of 156)bad_indirect_item: block 1907661: item 7659550 76756x1 IND (1), len 8, location 3056 entry count 0, fsck need 0, format new has a pointer 0 to the block 1 whichin tree already bad_indirect_item: block 1907661: item 7659550 7675670 0x1 IND (1), len 8, location 3056 entry count 0, fsckd 0, format new has a pointer 1 to the block 500 which is in tree already bit 2535358884, bitsize 314620004 reiserfsck: bitmap.c:160: reiserfs_bitmap_test_bit: Assertion `bit_number bm-bm_bit_size' failed. Aborted (core dumped) -- Best regards, Vitaly Use more recent version please. ftp://ftp.namesys.com/pub/reiserfsprogs/reiserfsprogs-3.6.4.tar.gz -- Yury Umanets
[reiserfs-list] My gpg public key
-BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org mQGiBDz0x1YRBADxB+UQ0YaqSlDXShVwmQ7xvEBHfhQymj3sD5qnmrt2DcYQpwWo BPjDc7NUTm2gfZc9tMzD5WzZGChY6ubSUl/WzhxAgP24R27B2pvJJvQAFGqFCbey ED9HLk0i95y50htSGhMISe4MYfbR29FVFNWiBTxV+JPPW5+rQnJnxUHHpwCgwJSU CWEiY+NCAdVkIv1Le3ifukkEALM4XreCNSnjoUT0TiqkbO3CE2ShvsegNmRNiYKp GcSoTApdQAq00GRrVtoXJUaHLKfkU348QrLTalgiwKm6VYWKMdzzJ6GUpxlYVOhK nGNjTkNPxrVNbdPW2s0Isc7Z0ASp/RMdGzGnsy8N6cG2b9HHR1/jP6MkZAY3zohg z+4aA/9Z0d6V25p5jqjuwwiOWiJSUCf5wJckIGtiNzg28HE+qpupU+C38AwmQr2B YY8YwvL6Jmi9WkvSwu5sGDxaapijQppFO4VxILfk0TFCiIs7xVQ6CsBNmmVnddWq HLyikQAjaZ4OfopeSkNgtLgZakxE79FqlHZph4x1nCIsNYBtDLQfWXVyeSBVbWFu ZXRzIDx1bWthQGFsdGxpbnV4LnJ1PohXBBMRAgAXBQI89MdWBQsHCgMEAxUDAgMW AgECF4AACgkQ96QCXp+d6dKWawCgmkdEufLYlAv0gy0x/NGSTXa7v6EAn0ZSVHEc JiqhPAxs30X/kNXU7JsTuQENBDz0x1gQBAD+qDFqt3P5DejhcE1omAvHZaW7h4Zl NWL8o9/X5rwIkQKu2OC20561QAyynCFyUJhdCrQdTCqeY+XrLV2kbLxx5CW/S20X xB86joN9YWFaSCFyBc+eIAByvnL5o0uym2J6XCVRymTqGA1tnYu9fmhioqNfXLYF IEF/+rByZnGzzwAEDQQAr7nPNhvNQQRvNA4Qfyrhc1S7y9BKFNTE0OlIoqhInqlv 56AfvoGcL1NuiET3yKjkeBDSmxzOqEg7QvdIiNXjkazW4jsPB4vdeRUmGCOnKazO pKloIdN10PnUMOiRttXLWzxsfTLt8ugTm+/+TtOrHDmm1Id5wlF5MJSuWNDgfB6I RgQYEQIABgUCPPTHWAAKCRD3pAJen53p0qLeAJ9B1FL2Eb+bUYnQuL4ar6E8yp3g DwCdG85Bir1K8luDSVpcwDLwZUCO4yo= =dx6Q -END PGP PUBLIC KEY BLOCK-
