Re: reiser4 bug
On Sun, Feb 27, 2005 at 07:34:11PM +, Szabolcs Illes wrote: Hi All, I have been using reiser4fs for 4 months without any problem since today. After tryinig to open a movie with mplayer a have this in my log: no other reiser4 messages in the log for 4 months? like delimiting keys mismatch reports? there was wrong bitmap checksum. actually I haven't seen such reports until now. are you sure your computer's disk/ram work well? Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: write_sd_by_inode_common (fs/reiser4/plugin/object.c:480)[nikita-2221]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to save sd for 1599330: -5 Feb 27 14:00:22 sunset kernel: reiser4[mc(9192)]: create_child_common (fs/reiser4/plugin/dir/dir.c:501)[nikita-2219]: Feb 27 14:00:22 sunset kernel: WARNING: Failed to create sd for 1599330 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:23 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:23 sunset kernel: WARNING: Wrong level found in node: 1 != 95 Feb 27 14:00:24 sunset kernel: reiser4[cupsd(3296)]: parse_node40 (fs/reiser4/plugin/node/node40.c:767)[nikita-494]: Feb 27 14:00:24 sunset kernel: WARNING: Wrong level found in node: 1 != 95 .. 1000x times were there unclear reboots? That shouldn't be a problem unless disk write caching is disabled. After trying to reboot: http://nuk.teteny.elte.hu/~selli/dscf0437.jpg (using 2.6.9-cko3) http://nuk.teteny.elte.hu/~selli/dscf0438.jpg http://nuk.teteny.elte.hu/~selli/dscf0439.jpg I had to install a new root filesystem, and using that I was able to fix the filesystem. ( --build-sb, build-fs, and fix ) I have lost some file but fortunatly I was able to use my system again. The affair happend when I was using 2.6.10 with reiser4 patch(from namesys.com). I tried to reboot with my previos kernel (2.6.9-cko3) but had the some bug (see screenshots). Sorry but I forgot to save the outout of the fsck prog :(. If U need any information do not hesitate contacting me.( I am not on the mailing list) Some info in advanve: Hardware: Dell Inpiron 8600c (1600Mhz Centrion processor) Kernel config: [...] -- Alex.
Re: Install errors, reiser3 messages
Clifford Beshers wrote: We recently rewrote our installer to use a custom program that can stream a compressed iso9660 image file and unpack it to disk. Previously it used rsync. Everything seemed to be fine, but when we started running it on many machines, we started encountering errors like the ones shown below, the output of dmesg. At first I suspected it might be that the kernel hadn't re-read the partition table, but on several installs we did not create or modify that table. Anyone have any guesses as to what is going wrong? Again, this is reiser3. hda1: rw=0, want=116654088, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=116916232, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=117178376, limit=50058477 ReiserFS: hda1: warning: sh-2029: reiserfs read_bitmaps: bitmap block (#6258688) reading failed ReiserFS: hda1: warning: jmacd-8: reiserfs_fill_super: unable to read bitmap The above look like hardware errors from the disk drive. There have been rsync related emails on this list, but let's start with a working disk drive, ok? It is remotely possible that the above could be a failure to reboot after using fsync NTFS volume version 1.2. NTFS-fs warning (device hda2): load_system_files(): Volume is dirty. Will not be able to remount read-write. Run chkdsk and mount in Windows. ReiserFS: hda1: found reiserfs format 3.6 with standard journal ReiserFS: hda1: using ordered data mode ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda1: checking transaction log (hda1) ReiserFS: hda1: Using r5 hash to sort names ReiserFS: hda1: warning: Created .reiserfs_priv on hda1 - reserved for xattr storage. Adding 1049592k swap on /mnt/install/boot/linux-swap.swp. Priority:-1 extents:215 ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 170, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? -- This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender and delete the message. Thank you.
Re: Install errors, reiser3 messages
Hans Reiser wrote: It is remotely possible that the above could be a failure to reboot after using fsync Err, fdisk not fsync
Re: Install errors, reiser3 messages
Well, I have some new info this morning. We attributed the errors to hard drive problems to start with as well, but the errors were too consistent and appeared on too many machines simultaneously. Over the weekend we have collected many reports of people being unable to install using reiser3, but succeeding with reiser4. This eliminates both bad CD burns and hard drive errors, so I went looking for another cause. Recently we included qtparted which pulls in a Debian package called ``progsreiserfs'' instead of ``reiserfsprogs.'' We are investigating this as the cause of the problems right now. We are seeing a behavior with the ``progsreiserfs'' tools that one install will generate errors, another will succeed but take a long time, and a third will succeed in the normal amount of time. Same machine, same hard disk, same CDROM. I'm including Debian's description of these packages below. Package: reiserfsprogs Status: install ok installed Priority: optional Section: admin Installed-Size: 1072 Maintainer: Ed Boraas [EMAIL PROTECTED] Architecture: i386 Version: 1:3.6.19-1 Depends: libc6 (= 2.3.2.ds1-4), libuuid1 Description: User-level tools for ReiserFS filesystems This package contains utilities to create, check, resize, and debug ReiserFS filesystems. . NOTE: Releases of Linux prior to 2.4.1 do not support ReiserFS on their own. Thus, these tools will only be useful with Linux 2.4.1 or later, or if your kernel has been built with the ReiserFS patch applied. This patch can be found in the appropriate kernel-patch-version-reiserfs packages. . Homepage: http://www.namesys.com/ zz:~# apt-cache show progsreiserfs Package: progsreiserfs Version: 0.3.0.4-4 Architecture: i386 Priority: extra Section: admin Maintainer: Jose Luis Tallon [EMAIL PROTECTED] Depends: libc6 (= 2.3.2.ds1-4), libreiserfs0.3-0 (= 0.3.0), libuuid1 Conflicts: reiserfsprogs Provides: reiserfsprogs Size: 34236 Installed-Size: 156 MD5sum: 57feec6fc2b48d125e755e0a2ab31bb0 Description: Tools for manipulating ReiserFS filesystems progsreiserfs is a collection of tools for manipulating ReiserFS filesystems. There are tools to create, check, resize, tune and copy ReiserFS filesystems. . These tools differ from the standard Namesys ReiserFS tools in that they use libreiserfs to do their work. Filename: pool/p/progsreiserfs/progsreiserfs_0.3.0.4-4_i386.deb Hans Reiser wrote: Clifford Beshers wrote: We recently rewrote our installer to use a custom program that can stream a compressed iso9660 image file and unpack it to disk. Previously it used rsync. Everything seemed to be fine, but when we started running it on many machines, we started encountering errors like the ones shown below, the output of dmesg. At first I suspected it might be that the kernel hadn't re-read the partition table, but on several installs we did not create or modify that table. Anyone have any guesses as to what is going wrong? Again, this is reiser3. hda1: rw=0, want=116654088, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=116916232, limit=50058477 attempt to access beyond end of device hda1: rw=0, want=117178376, limit=50058477 ReiserFS: hda1: warning: sh-2029: reiserfs read_bitmaps: bitmap block (#6258688) reading failed ReiserFS: hda1: warning: jmacd-8: reiserfs_fill_super: unable to read bitmap The above look like hardware errors from the disk drive. There have been rsync related emails on this list, but let's start with a working disk drive, ok? It is remotely possible that the above could be a failure to reboot after using fsync NTFS volume version 1.2. NTFS-fs warning (device hda2): load_system_files(): Volume is dirty. Will not be able to remount read-write. Run chkdsk and mount in Windows. ReiserFS: hda1: found reiserfs format 3.6 with standard journal ReiserFS: hda1: using ordered data mode ReiserFS: hda1: journal params: device hda1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 ReiserFS: hda1: checking transaction log (hda1) ReiserFS: hda1: Using r5 hash to sort names ReiserFS: hda1: warning: Created .reiserfs_priv on hda1 - reserved for xattr storage. Adding 1049592k swap on /mnt/install/boot/linux-swap.swp. Priority:-1 extents:215 ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 170, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150: search_by_key: invalid format found in block 5439488. Fsck? ReiserFS: warning: is_leaf: item location seems wrong (second one): *3.6* [7 32 0x1 DIRECT], item_len 169, item_location 3388, free_space(entry_count) 65535 ReiserFS: hda1: warning: vs-5150:
Re: where are reiser4 sources
Mark Junker wrote: Rudy Zijlstra schrieb: Have you checked the Windows licenses (or rather the needed windows development kits) and what they allow you to do? If i remember correctly you run into problems there as well... Just to let you know: The ReactOS license it GPL too. Everything's clear now? May I now use the Reiser4 sources to develop a driver for ReactOS? Regards, Mark Well, it seems I misunderstood. I assumed you were using proprietary OS components. So long as the whole OS is GPL'd, you can use Reiser4. If however, MS is being paid license fees, you must pay me fees too. I am frankly skeptical that one should attempt to clone windows. Hans
Re: where are reiser4 sources
On Mon, 28 Feb 2005 15:41:52 PST, Hans Reiser said: I am frankly skeptical that one should attempt to clone windows. That explains why WINE exists, I guess.. ;) pgpzJsM1Ca7pO.pgp Description: PGP signature
Re: Mail System Error - Returned Mail
you should not send such responses if an address is likely spoofed. in any case, there were no included instructions for protection or detail as to the messages of problematic quantity and undesired content. On Thursday 24 February 2005 09:57, [EMAIL PROTECTED] wrote: Dear user reiserfs-list@namesys.com, Your e-mail account was used to send a large amount of spam messages during this week. Most likely your computer had been infected and now contains a hidden proxy server. Please follow the instructions in order to keep your computer safe. Best regards, namesys.com user support team.
Re:
Softw.are: GRAPHI.CS AND PUBLISHING, OFFICE SOF.TWARE You gotta see this - http://acerbic.boundarybeyondwhich.com/?a=680arsenic
