I used the mkpartfs command in parted to create some reiserfs partitions on a disk. I then checked the file system on one of the partitions with fsck, and this is what I get:
Code:
root@ttyp0[knoppix]# fsck /dev/hda2
fsck 1.35 (28-Feb-2004)
reiserfsck 3.6.18 (2003 w w w . 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 w w w. namesys. com/support.html. **
*************************************************************
Will read-only check consistency of the filesystem on /dev/hda2
Will put log info to 'stdout'
Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes
###########
reiserfsck --check started at Sun Sep 19 11:29:03 2004
###########
Replaying journal..
No transactions found
Checking internal tree..finished
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.
Checking Semantic tree:
finished
1 found corruptions can be fixed when running with --fix-fixable
###########
reiserfsck finished at Sun Sep 19 11:29:06 2004
###########
root@ttyp0[knoppix]#
Does anyone know why a freshly created file system would already have a corruption? I see that it is "fixable", but it seems like this should not happen.
P.S. I added the spaces in "w w w" in the above listing so I could submit this question.
