Problem with mkreiserfs
Hi Folks, I have a device of size 5219263 blocks (each of size of 4096, Actually it has 41754107 blocks each of size 512 bytes. I just converted it into 4k blcok). When I try to create reiserfs file system on this device it reporting ERROR message that there are no enough blocks on the device. I tried the following command #mkfs -t reiserfs -b 4096 /dev/sda1 5219263 On the same device I am able to Ext2/Ext3 file system with out any problem #mkfs -t ext3 -b 4096 /dev/sda1 5219263 // this command running with out any problem. Why I am getting problem with reiserfs file system Your help is appreciated. Thanks in advance Regards Masthan
BUG IN REISERFS
Hi Folks, Mkreiserfs command is failing by showing There are no enoguh blocks on this device , What is the minimum size of a disk to create reiserfs file system Regards, Masthan
BUG: reiserfsck --check fails exit status=6
Hi, I am using SUSE 10 beta version. I ran reiserfsck command with the following options reiserfsck --check -q -y -n /dev/sdb1 21 O/p of the command look like this. reiserfsck 3.6.19 (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/sdb1 Will put log info to 'stdout' reiserfsck --check started at Mon May 29 13:16:40 2006 Relaying journal.. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed checking internal tree..finished Comparing bitmaps..Checking Semantic tree: finished 26 found corruptions can be fixed when running with --fix-fixable reiserfsck finished at Mon May 29 13:16:44 2006 reiserfsck exit status = 6 Can any one Explain this ..Why it happened ? Your help is appreciated Regards, Masthan
RE: Try to fix a broken ReiserFS / Data Recovering?
Hi, The following paragraph is snippet of reiserfsck man page. AN EXAMPLE OF USING reiserfsck 1. You think something may be wrong with a reiserfs partition on /dev/hda1 or you would just like to perform a periodic disk check. 2. Run reiserfsck --check --logfile check.log /dev/hda1. If reiserfsck --check exits with status 0 it means no errors were discovered. 3. If reiserfsck --check exits with status 1 (and reports about fixable corruptions) it means that you should run reiserfsck --fix-fixable --logfile fixable.log /dev/hda1. 4. If reiserfsck --check exits with status 2 (and reports about fatal corruptions) it means that you need to run reiserfsck --rebuild-tree. If reiserfsck --check fails in some way you should also run reiserfsck --rebuild-tree, but we also encourage you to submit this as a bug report. 5. Before running reiserfsck --rebuild-tree, please make a backup of the whole partition before proceeding. Then run reiserfsck --rebuild-tree --logfile rebuild.log /dev/hda1. 6. If the reiserfsck --rebuild-tree step fails or does not recover what you expected, please submit this as a bug report. Try to provide as much information as possible including your platform and Linux kernel version. We will try to help solve the problem. EXIT CODES reiserfsck uses the following exit codes: 0 - No errors. 1 - File system errors corrected. 2 - Reboot is needed. 4 - File system fatal errors left uncorrected, reiserfsck --rebuild-tree needs to be launched. 6 - File system fixable errors left uncorrected, reiserfsck --fix-fixable needs to be launched. 8 - Operational error. 16 - Usage or syntax error. AUTHOR This version of reiserfsck has been written by Vitaly Fertman [EMAIL PROTECTED]. BUGS Please report bugs to the ReiserFS developers [EMAIL PROTECTED], providing as much information as possible--your hardware, kernel, patches, settings, all printed messages, the logfile; check the syslog file for any related information. TODO Faster recovering, signal handling. From the fourth point What I understood is, failure of reiserfsck --check with error code other than 1 and 2 is a bug. Is it correct ? And the last table tells that reiserfsck still not hadling signals. Is it correct ? Regards, Masthan -Original Message- From: Vladimir V. Saveliev [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 5:58 PM To: Lars Wolff Cc: reiserfs-list@namesys.com Subject: Re: Try to fix a broken ReiserFS / Data Recovering? Hello On Mon, 2006-06-19 at 11:28 +0200, Lars Wolff wrote: Hi there, i am very new to this list, i just signed up today, because i got some problems with a broken ReiserFS since yesterday. _The problem_ Yesterday my Router/Server (Suse Linux 8.1, 40GB IDE HDD with ReiserFS) hang up. After a reboot it only starts to load stage2 of Grub, which fails and ends up in the grub minimal bash. _What i do to resolve the problem_ I downloaded the Suse Live-CD 9.1 and did a clean boot from it. I Try to mount the volume, what end up with Falscher Dateisystemtyp, ungültige Optionen, der »Superblock« von /dev/hdb2 ist beschädigt oder es sind zu viele Dateisysteme eingehängt (=corrupt superblock) Then I tried reiserFs Check wich ends up in: Bad root block 0. (--rebuild-tree did not complete). Ok, i followed the instructions in the following bad block info text and did a reiserFs -B badblocksfile --rebuild-tree. Wich aborts and said badblock in . Right now i am doing a complete Backup image with dd_rescue, after this i would like to run /sbin/badblocks, as explained in the Faq (http://www.namesys.com/bad-block-handling.html) and run then reiserfs -B again. _My Questions_ - Am i right in doing these actions to try to resolve the problem of my harddisk, and HOPEFULLY to recover the Data? after dd_rescue completes - please run reiserfsck (3.6.19, without any options but filename) on backup image and let us know what it says. - Is there anything i should try/do else? - Do you now somebody/any company, wich do a real data-recovering von ReiserFS Disk? Its only 40GB but there are some data on it wich are very important. (don't ask after the backups, they broke last week on the extern hdd! :(( ) Hopefully you guys can help me, thanks a lot :) Lars
RE: BUG: reiserfsck --check fails exit status=6
Hi Vladimir, Thanks for your help . Now it is running fine.. Regards, Masthan -Original Message- From: Vladimir V. Saveliev [mailto:[EMAIL PROTECTED] Sent: Monday, June 19, 2006 6:13 PM To: Masthan, Dudekula (STSD) Cc: reiserfs-list@namesys.com Subject: Re: BUG: reiserfsck --check fails exit status=6 Hello On Mon, 2006-06-19 at 14:50 +0530, Masthan, Dudekula (STSD) wrote: Hi, I am using SUSE 10 beta version. I ran reiserfsck command with the following options reiserfsck --check -q -y -n /dev/sdb1 21 O/p of the command look like this. reiserfsck 3.6.19 (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/sdb1 Will put log info to 'stdout' reiserfsck --check started at Mon May 29 13:16:40 2006 Relaying journal.. Reiserfs journal '/dev/sdb1' in blocks [18..8211]: 0 transactions replayed checking internal tree..finished Comparing bitmaps..Checking Semantic tree: finished 26 found corruptions can be fixed when running with --fix-fixable reiserfsck finished at Mon May 29 13:16:44 2006 reiserfsck exit status = 6 Can any one Explain this .. reiserfsck has 3 major modes. By default (or with --check) it checks filesystem and either says that everything is ok, or reiserfsck has to be run with --fix-fixable (when filesystem can be fixed without tree rebuiling) or with --rebuild-tree when corruptions can be recovered only via complete tree rebuild. Why it happened ? Can you re-run reiserfsck --check without -n and with -l logfile and let us see what you get in logfile? Your help is appreciated Regards, Masthan
RE: Bug#369285: reiserfsprogs: can't mount reiserfs volume with 8kb block size
Hi Domenico, Currently ReiserFS supports 4 KB block only. Following link will explain you more on this. www.oracle.com/technology/pub/articles/calish_filesys.html Kindly come back, still if you have any doubts Regards, Masthan -Original Message- From: Domenico Andreoli [mailto:[EMAIL PROTECTED] Sent: Monday, May 29, 2006 11:58 AM To: Andreas Beckmann Cc: reiserfs-list@namesys.com; [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Bug#369285: reiserfsprogs: can't mount reiserfs volume with 8kb block size forwarded 369285 reiserfs-list@namesys.com merge 304342 369285 thanks On Sun, May 28, 2006 at 11:03:11PM +0200, Andreas Beckmann wrote: Hi, hi Andreas, I just created a new reiserfs volume with the following command: mkreiserfs -d -l backup -b 8192 /dev/hda11 but mounting it fails with the error: mount: wrong fs type, bad option, bad superblock on /dev/hda11, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so and dmesg says: ReiserFS: hda11: warning: sh-2011: read_super_block: can't find a reiserfs filesystem on (dev hda11, block 32, size 2048) ReiserFS: hda11: warning: sh-2021: reiserfs_fill_super: can not find reiserfs on hda11 Other blocksizes just work fine. that block sizes different from 4k do not work is a known problem, please see bug #304342. last news i heard about this is of more than a year ago. Vitaly, maybe you have a nice release under the cover? :) cheers domenico -[ Domenico Andreoli, aka cavok --[ http://people.debian.org/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
