Partial data loss with reiserfs3

Partial data loss with reiserfs3

[Laurynas Biveinis]

Hello,

I was trying to move data from my NTFS partition to Linux (Fedora Core
3).   I had 2GB ext3 partition for /home. After copying some files from
NTFS partition to /home and successfully shrinking NTFS partition by
4GB I wanted to enlarge my /home. Ext3 does not support partition
resize and move there, so I have decided to switch /home to ReiserFS
v3 (That's the version available for FC3)

I've created 4GB Reiser partition (/dev/hda6) and moved data there from
old /home (/dev/hda7):
umount /home
mkdir /home.old
mount /dev/hda7 /home.old
mount /dev/hda6 /home
cd /home.old
find . -depth -print0 | cpio --null -pvd /home

It worked OK (as in "cpio did not fail and I could see my directories
and files")

Then I deleted my old /dev/hda7, and tried to enlarge /dev/hda6 to take
its space - by resizing partition, then by resizefs.reiserfs. Resizefs
complained about "Error: Can't resize filesystem outside the device."
no matter what I size I would try to expand it, and with '-f' option
too.  It occured to me that perhaps reboot might be required there, so
I rebooted. Bingo, after reboot resizefs enlarged partition to the size
I wanted. Reboot once again and try to login with ordinary user (whose
home is on that partition).

Login got to the point of KDE "Restoring session state" and then PC
hanged. Hmm. Reboot and retry login with non-root user. The same.
Reboot and log-in as root.

[root@laurynas-pc ~]# umount /home
[root@laurynas-pc ~]# reiserfsck /dev/hda6

[See Output 1 below]

OK, so it says --rebuild-tree...

[root@laurynas-pc ~]# reiserfsck --rebuild-tree /dev/hda6

[See Output 2 below]

At this point I remounted partition read-only and looked around. And
that's it, part of my data is at lost+found, and part is gone. 
Here was a typical mount /dev/hda6 output to syslog:
-----------------
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: found reiserfs
format "3.6" with standard journal
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: using ordered data
mode
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: journal params:
device hda6, size 8192, journal first block 18, max trans len 1024, max
batch 900, max commit age 30, max trans age 30
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: checking transaction
log (hda6)
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: replayed 17
transactions in 0 seconds
Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: Using r5 hash to
sort names
---------------

And one more line looks particularly interesting:
---------------
Feb 13 18:08:05 laurynas-pc kernel: ReiserFS: hda6: warning: vs-4080:
reiserfs_free_block: free_block (hda6:32998)[dev:blocknr]: bit already
cleared
---------------

Is there anything I can do to look for my other missing data?

TIA,
Laurynas

------------------------------------------
Output 1:
------------------------------------------
reiserfsck 3.6.18 (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/hda6
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 Feb 13 18:13:57 2005
###########
Replaying journal..
Reiserfs journal '/dev/hda6' in blocks [18..8211]: 0 transactions
replayed
Zero bit found in on-disk bitmap after the last valid bit.
Checking internal tree../  1 (of   7)/  2 (of 163)bad_leaf: block 32978,
items 0 and 1: The wrong order of items: [2 6 0x1 DRCT (2)], [2 12 0x1
IND (1)]
bad_leaf: block 32978, items 1 and 2: The wrong order of items: [2 12
0x1 IND (1)], [2 112 0x1 IND (1)]
bad_path: The right delimiting key [2 18 0x0 SD (0)] of the node (32978)
must be greater than the last (2) element's key [2 112 0x1 IND (1)]
within the node.
/ 14 (of 163)bad_path: The left delimiting key [2 112 0x1 IND (1)] of
the node (32769) must be equal to the first element's key [2 1681
0xa1d001 IND (1)] within the node.
/106 (of 163)bad_indirect_item: block 32872: The item (2 818 0x1 IND
(1), len 8, location 3364 entry count 0, fsck need 0, format new) has
the bad pointer (0) to the block (34816), which is in tree already
bad_indirect_item: block 32872: The item (2 818 0x1 IND (1), len 8,
location 3364 entry count 0, fsck need 0, format new) has the bad
pointer (1) to the block (34817), which is in tree already
/  2 (of   7)/ 65 (of 163)bad_node: vpf-10350: The block (32769) is used
more than once in the tree.
 the problem in the internal node occured (32769), whole subtree is
skipped
finished
Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps
differs.
Bad nodes were found, Semantic pass skipped
5 found corruptions can be fixed only when running with --rebuild-tree
###########
reiserfsck finished at Sun Feb 13 18:14:03 2005
###########


--------------------------------------------------
Output 2:
--------------------------------------------------

[root@laurynas-pc ~]# reiserfsck --rebuild-tree /dev/hda6
reiserfsck 3.6.18 (2003 www.namesys.com)

*************************************************************
** Do not  run  the  program  with  --rebuild-tree  unless **
** something is broken and MAKE A BACKUP  before using it. **
** If you have bad sectors on a drive  it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive  to the good one -- dd_rescue is  a good tool for **
** that -- and only then run this program.                 **
** 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 rebuild the filesystem (/dev/hda6) tree
Will put log info to 'stdout'

Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
Replaying journal..
Reiserfs journal '/dev/hda6' in blocks [18..8211]: 0 transactions
replayed
Zero bit found in on-disk bitmap after the last valid bit. Fixed.
###########
reiserfsck --rebuild-tree started at Sun Feb 13 18:14:45 2005
###########

Pass 0:
####### Pass 0 #######
Loading on-disk bitmap .. ok, 275702 blocks marked used
init_source_bitmap: Bitmap 38 (of 32768 bits) is wrong - mark all blocks
[1245184 - 1277952] as used
init_source_bitmap: Bitmap 39 (of 32768 bits) is wrong - mark all blocks
[1277952 - 1310720] as used
init_source_bitmap: Bitmap 45 (of 32768 bits) is wrong - mark all blocks
[1474560 - 1507328] as used
init_source_bitmap: Bitmap 46 (of 32768 bits) is wrong - mark all blocks
[1507328 - 1540096] as used
init_source_bitmap: Bitmap 48 (of 32768 bits) is wrong - mark all blocks
[1572864 - 1605632] as used
init_source_bitmap: Bitmap 51 (of 32768 bits) is wrong - mark all blocks
[1671168 - 1703936] as used
init_source_bitmap: Bitmap 52 (of 32768 bits) is wrong - mark all blocks
[1703936 - 1736704] as used
init_source_bitmap: Bitmap 53 (of 4332 bits) is wrong - mark all blocks
[1736704 - 1741036] as used
Skipping 8264 blocks (super block, journal, bitmaps) 442629 blocks will
be read
0%....20%....40%.block 1410673: The number of items (2560) is incorrect,
shouldbe (1) - corrected
block 1410673: The free space (2) is incorrect, should be (2512) -
corrected
pass0: vpf-10110: block 1410673, item (0): Unknown item type found
[201331327 167772161 0x2 ??? (15)] - deleted
...60%....80%....100%                        left 0, 3184 /sec
464 directory entries were hashed with "r5" hash.
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 442629
                Leaves among those 95
                        - leaves all contents of which could not be
saved and deleted 1
                Objectids found 620

Pass 1 (will try to insert 94 leaves):
####### Pass 1 #######
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100%                          left 0,
94 /sec
Flushing..finished
        94 leaves read
                94 inserted
####### Pass 2 #######
Flushing..finished
Pass 3 (semantic):
####### Pass 3 #########
/lauras/.mc/inivpf-10680: The file [2 6] has the wrong block count in
the StatData (8) - corrected to (0)
rebuild_semantic_pass: The entry [2 7] ("Tree") in directory [2 5]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 8] ("cedit") in directory [2 5]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 9] ("filepos") in directory [2 5]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 10] ("history") in directory [2 5]
points to nowhere - is removed
vpf-10650: The directory [2 5] has the wrong size in the StatData (168)
- corrected to (72)
rebuild_semantic_pass: The entry [2 11] (".qt") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 16] ("TeX") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 18] ("bin") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 32] ("doc") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 34] (".kde") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 296] (".ssh") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 307] ("bash_completion_svn") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 308] (".amsn") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 322] (".dmrc") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 323] (".gaim") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 638] (".java") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 656] (".mcop") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 804] (".wine") in directory [2 4]
points tonowhere - is removed
rebuild_semantic_pass: The entry [2 1018] (".xine") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1023] (".xmms") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1029] (".tuxracer") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1031] (".bashrc") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [2 1032] (".gnome2_private") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1033] ("olimp") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1428] (".openoffice-install-log") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1429] (".freeciv") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 1434] (".mozilla") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1741] (".gconfd") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1743] (".gnochm") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1747] (".gnome2") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1768] (".civserver_history") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1769] (".gstreamer-0.8") in
directory [2 4]points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1772] ("TeX-LT") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1795] ("TeX-VU") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1814] ("todo ispell-lt.txt") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1815] (".acrobat") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1817] (".mcoprc") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1818] (".gnucash") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1822] (".bash_logout") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1823] (".gtk-bookmarks") in
directory [2 4]points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1824] (".AbiSuite") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1827] (".viminfo") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1828] ("Desktop") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1836] (".vmware") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1840] (".amyedit") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1841] (".xemacs") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 1843] (".esd_auth") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1844] (".ispell_lietuviu") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1845] ("uosis.mif.vu.lt") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1938] ("latex-lt.doc") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1939] ("latex-lt.sxw") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1940] (".rhn-applet") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1943] (".bash_history") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1944] (".rhn-applet.conf") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 1945] (".thunderbird") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 2370] (".civclientrc") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [2 283] (".DCOPserver_laurynas-pc__0")
in directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 2371] ("fps-linux") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3645] (".hxplayerrc") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3646] (".openoffice-lock") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3647] (".thumbnails") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3651] (".mime.types") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3652] (".gnome_private") in
directory [2 4]points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3653] (".sversionrc") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3654] (".recently-used") in
directory [2 4]points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3655] ("old-src") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 3723] ("Finance") in directory [2 4]
pointsto nowhere - is removed
rebuild_semantic_pass: The entry [4 3725] (".adobe") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3727] (".emacs") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3728] (".gconf") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3767] (".fonts") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3777] (".gnome") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3810] (".gtkrc") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3811] ("ims.mii.lt") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3885] (".subversion") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3893] (".zshrc") in directory [2 4]
points to nowhere - is removed
rebuild_semantic_pass: The entry [4 3894] (".rhopenoffice1.1") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4001] ("AceMoney sn.txt") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4002] (".bash_profile") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4003] (".saves-17574-laurynas-pc")
in directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4004] ("torrents") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4006] ("mirc-logs") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4229] (".cvspass") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4230] ("Windows XP Professional") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4238] (".Maelstrom-data") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4239] ("projektai.txt") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4240] (".eggcups") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4241] (".xsession-errors") in
directory [2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4242] (".fonts.conf") in directory
[2 4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4243] (".emacs.d") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4245] ("lazybones") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4325] (".mailcap") in directory [2
4] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4327] ("texbytopic-a4.pdf") in
directory [24] points to nowhere - is removed
rebuild_semantic_pass: The entry [4 4328] ("installs") in directory [2
4] points to nowhere - is removed
vpf-10680: The directory [2 4] has the wrong block count in the StatData
(6) - corrected to (1)
vpf-10650: The directory [2 4] has the wrong size in the StatData (2768)
- corrected to (216)
Flushing..finished
        Files found: 4
        Directories found: 5
        Symlinks found: 1
        Names pointing to nowhere (removed): 93
Pass 3a (looking for lost dir/files):
####### Pass 3a (lost+found pass) #########
Looking for lost directories:
/1438_1689get_next_directory_item: The entry ".." of the directory [1438
1689] pointes to [2 1438], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [1438 1691] ("overlayinfo") in
directory [14381689] points to nowhere - is removed
vpf-10650: The directory [1438 1689] has the wrong size in the StatData
(112) -corrected to (80)
/1949_2319get_next_directory_item: The entry ".." of the directory [1949
2319] pointes to [4 1949], instead of [2 4335] - corrected
/1949_2333get_next_directory_item: The entry ".." of the directory [1949
2333] pointes to [4 1949], instead of [2 4335] - corrected
/1949_2363get_next_directory_item: The entry ".." of the directory [1949
2363] pointes to [4 1949], instead of [2 4335] - corrected
/1953_2063get_next_directory_item: The entry ".." of the directory [1953
2063] pointes to [4 1953], instead of [2 4335] - corrected
/Inbox.sbdrebuild_semantic_pass: The entry [2069 2070] ("MII") in
directory [2063 2069] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2071] ("Alna") in directory [2063
2069] points to nowhere - is removed
/Mailing Listai.sbd/Durdomai.sbd/group4infvpf-10680: The file [2069
2137] has the wrong block count in the StatData (42816) - corrected to
(2320)
rebuild_semantic_pass: The entry [2069 2138] ("MIFFUX2001.msf") in
directory [2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2139] ("MIFFUX2001.sbd") in
directory [2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2140] ("Kino Akademija.msf") in
directory [2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2141] ("Kino Akademija.sbd") in
directory [2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2142] ("asm.msf") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2143] ("asm.sbd") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2144] ("Amazon.msf") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2145] ("Amazon.sbd") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2146] ("JPM.msf") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2147] ("JPM.sbd") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2148] ("Licejus.msf") in
directory [20692101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2149] ("Licejus.sbd") in
directory [20692101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2159] ("MIFFUX2001") in directory
[2069 2101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2160] ("VU mail.msf") in
directory [20692101] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2161] ("VU mail.sbd") in
directory [20692101] points to nowhere - is removed
vpf-10680: The directory [2069 2101] has the wrong block count in the
StatData (4) - corrected to (3)
vpf-10650: The directory [2069 2101] has the wrong size in the StatData
(1576) - corrected to (1112)
rebuild_semantic_pass: The entry [2069 2162] ("Wholenote") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2163] ("FPS.msf") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2164] ("FPS.sbd") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2165] ("AceMoney.msf") in
directory [2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2166] ("AceMoney.sbd") in
directory [2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2167] ("ALP.msf") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2168] ("ALP.sbd") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2169] ("Development.msf") in
directory [2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2069 2170] ("Development.sbd") in
directory [2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2092 2210] ("Bass.msf") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2092 2211] ("Bass.sbd") in directory
[2069 2092] points to nowhere - is removed
rebuild_semantic_pass: The entry [2092 2212] ("Durdomai") in directory
[2069 2092] points to nowhere - is removed
vpf-10680: The directory [2069 2092] has the wrong block count in the
StatData (2) - corrected to (1)
vpf-10650: The directory [2069 2092] has the wrong size in the StatData
(632) -corrected to (304)
rebuild_semantic_pass: The entry [2069 2213] ("Mailing Listai") in
directory [2063 2069] points to nowhere - is removed
vpf-10650: The directory [2063 2069] has the wrong size in the StatData
(392) -corrected to (312)
/Inboxvpf-10680: The file [2063 2215] has the wrong block count in the
StatData(215672) - corrected to (7120)
rebuild_semantic_pass: The entry [2063 2216] ("Trash") in directory
[1953 2063]points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2217] ("filterlog.html") in
directory [1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2218] ("Junk.msf") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2219] ("Junk.sbd") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2220] ("Templates.msf") in
directory [1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2221] ("Templates.sbd") in
directory [1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2222] ("Sent.msf") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2223] ("Sent.sbd") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2224] ("msgFilterRules.dat") in
directory [1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2225] ("Unsent Messages") in
directory [1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2226] ("Templates") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2227] ("Drafts.msf") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2228] ("Drafts.sbd") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2229] ("Trash.msf") in directory
[1953 2063] points to nowhere - is removed
rebuild_semantic_pass: The entry [2063 2230] ("junklog.html") in
directory [1953 2063] points to nowhere - is removed
vpf-10680: The directory [1953 2063] has the wrong block count in the
StatData (2) - corrected to (1)
vpf-10650: The directory [1953 2063] has the wrong size in the StatData
(736) -corrected to (288)
/1953_2231get_next_directory_item: The entry ".." of the directory [1953
2231] pointes to [4 1953], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [2231 2237] ("Microsoft.sbd") in
directory [1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2259] ("OpenTTD") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2260] ("Sysinternals.msf") in
directory [1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2261] ("Sysinternals.sbd") in
directory [1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2262] ("News.msf") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2263] ("News.sbd") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2273] ("feeditems.rdf") in
directory [1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2274] ("Microsoft") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2275] ("msgFilterRules.dat") in
directory [1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2276] ("feeds.rdf") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2277] ("Blogs.msf") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2278] ("Blogs.sbd") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2288] ("Trash.msf") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2289] ("Trash.sbd") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2290] ("OpenTTD.msf") in
directory [19532231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2291] ("OpenTTD.sbd") in
directory [19532231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2292] ("Mozilla") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2293] ("Fun.msf") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2294] ("Fun.sbd") in directory
[1953 2231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2304] ("Mozilla.msf") in
directory [19532231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2305] ("Mozilla.sbd") in
directory [19532231] points to nowhere - is removed
rebuild_semantic_pass: The entry [2231 2315] ("Sysinternals") in
directory [1953 2231] points to nowhere - is removed
vpf-10680: The directory [1953 2231] has the wrong block count in the
StatData (2) - corrected to (1)
vpf-10650: The directory [1953 2231] has the wrong size in the StatData
(840) -corrected to (176)
/2170_2189get_next_directory_item: The entry ".." of the directory [2170
2189] pointes to [2069 2170], instead of [2 4335] - corrected
/2170_2201get_next_directory_item: The entry ".." of the directory [2170
2201] pointes to [2069 2170], instead of [2 4335] - corrected
/3728_3729get_next_directory_item: The entry ".." of the directory [3728
3729] pointes to [4 3728], instead of [2 4335] - corrected
/3777_3778get_next_directory_item: The entry ".." of the directory [3777
3778] pointes to [4 3777], instead of [2 4335] - corrected
/3777_3807get_next_directory_item: The entry ".." of the directory [3777
3807] pointes to [4 3777], instead of [2 4335] - corrected
/3811_3812get_next_directory_item: The entry ".." of the directory [3811
3812] pointes to [4 3811], instead of [2 4335] - corrected
/text-baserebuild_semantic_pass: The entry [3811 3826]
("index.php.svn-base") in directory [3811 3824] points to nowhere - is
removed
vpf-10650: The directory [3811 3824] has the wrong size in the StatData
(120) -corrected to (80)
rebuild_semantic_pass: The entry [3811 3827] ("README.txt") in directory
[3811 3812] points to nowhere - is removed
rebuild_semantic_pass: The entry [3811 3828] ("prop-base") in directory
[3811 3812] points to nowhere - is removed
rebuild_semantic_pass: The entry [3811 3831] ("wcprops") in directory
[3811 3812] points to nowhere - is removed
vpf-10650: The directory [3811 3812] has the wrong size in the StatData
(296) -corrected to (208)
/3894_3895get_next_directory_item: The entry ".." of the directory [3894
3895] pointes to [4 3894], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [3895 3896] ("temp") in directory [3894
3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3897] ("database") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3900] ("basic") in directory
[3894 3895]points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3907] ("store") in directory
[3894 3895]points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3908] ("autocorr") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3909] ("autotext") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3911] ("template") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3912] ("uno_packages") in
directory [3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3913] ("backup") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3914] ("gallery") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3919] ("config") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3939] ("wordbook") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3941] ("plugin") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3942] ("registry") in directory
[3894 3895] points to nowhere - is removed
rebuild_semantic_pass: The entry [3895 3978] ("psprint") in directory
[3894 3895] points to nowhere - is removed
vpf-10650: The directory [3894 3895] has the wrong size in the StatData
(416) -corrected to (48)
/3894_3984get_next_directory_item: The entry ".." of the directory [3894
3984] pointes to [4 3894], instead of [2 4335] - corrected
/3942_3943get_next_directory_item: The entry ".." of the directory [3942
3943] pointes to [3895 3942], instead of [2 4335] - corrected
/3942_3954get_next_directory_item: The entry ".." of the directory [3942
3954] pointes to [3895 3942], instead of [2 4335] - corrected
/4246_4247get_next_directory_item: The entry ".." of the directory [4246
4247] pointes to [4245 4246], instead of [2 4335] - corrected
/propsvpf-10680: The directory [4246 4255] has the wrong block count in
the StatData (2) - corrected to (1)
vpf-10650: The directory [4246 4255] has the wrong size in the StatData
(560) -corrected to (48)
rebuild_semantic_pass: The entry [4246 4267] ("empty-file") in directory
[4246 4247] points to nowhere - is removed
rebuild_semantic_pass: The entry [4246 4268] ("entries") in directory
[4246 4247] points to nowhere - is removed
vpf-10650: The directory [4246 4247] has the wrong size in the StatData
(360) -corrected to (304)
/4307_4308get_next_directory_item: The entry ".." of the directory [4307
4308] pointes to [4245 4307], instead of [2 4335] - corrected
/4307_4313get_next_directory_item: The entry ".." of the directory [4307
4313] pointes to [4245 4307], instead of [2 4335] - corrected
/4307_4318get_next_directory_item: The entry ".." of the directory [4307
4318] pointes to [4245 4307], instead of [2 4335] - corrected
/4307_4321get_next_directory_item: The entry ".." of the directory [4307
4321] pointes to [4245 4307], instead of [2 4335] - corrected
Looking for lost files:
vpf-10680: The file [4328 4329] has the wrong block count in the
StatData (13208) - corrected to (2544)
Flushing..finished
        Objects without names 123
        Empty lost dirs removed 32
        Dirs linked to /lost+found: 21
        Files linked to /lost+found 102
Pass 4 - finished       done 0, 0 /sec
        Deleted unreachable items 40
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Sun Feb 13 18:17:09 2005
###########
[root@laurynas-pc ~]# reiserfsck /dev/hda6
reiserfsck 3.6.18 (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/hda6
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 Feb 13 18:17:36 2005
###########
Replaying journal..
Reiserfs journal '/dev/hda6' in blocks [18..8211]: 0 transactions
replayed
Checking internal tree..finished
Comparing bitmaps..finished
Checking Semantic tree:
finished
No corruptions found
There are on the filesystem:
        Leaves 93
        Internal nodes 1
        Directories 115
        Other files 291
        Data block pointers 36145 (0 of them are zero)
        Safe links 0
###########
reiserfsck finished at Sun Feb 13 18:17:39 2005
###########

Re: Partial data loss with reiserfs3

[Vitaly Fertman]

On Sunday 13 February 2005 20:29, Laurynas Biveinis wrote:
> Hello,
>
> I was trying to move data from my NTFS partition to Linux (Fedora Core
> 3).   I had 2GB ext3 partition for /home. After copying some files from
> NTFS partition to /home and successfully shrinking NTFS partition by
> 4GB I wanted to enlarge my /home. Ext3 does not support partition
> resize and move there, so I have decided to switch /home to ReiserFS
> v3 (That's the version available for FC3)
>
> I've created 4GB Reiser partition (/dev/hda6) and moved data there from
> old /home (/dev/hda7):
> umount /home
> mkdir /home.old
> mount /dev/hda7 /home.old
> mount /dev/hda6 /home
> cd /home.old
> find . -depth -print0 | cpio --null -pvd /home
>
> It worked OK (as in "cpio did not fail and I could see my directories
> and files")
>
> Then I deleted my old /dev/hda7, and tried to enlarge /dev/hda6 to take
> its space - by resizing partition, then by resizefs.reiserfs. Resizefs
> complained about "Error: Can't resize filesystem outside the device."
> no matter what I size I would try to expand it, and with '-f' option
> too.  It occured to me that perhaps reboot might be required there, so
> I rebooted. Bingo, after reboot resizefs enlarged partition to the size
> I wanted. Reboot once again and try to login with ordinary user (whose
> home is on that partition).


reboot is required between repartitioning a drive and starting to use 
moved/created partitions. without that the kernel may continue to use
old partition table. so it would be great to recall step-by-step history 
of your copings, removes, repatitionings and reboots.


> Login got to the point of KDE "Restoring session state" and then PC
> hanged. Hmm. Reboot and retry login with non-root user. The same.
> Reboot and log-in as root.
>
> [root@laurynas-pc ~]# umount /home
> [root@laurynas-pc ~]# reiserfsck /dev/hda6
>
> [See Output 1 below]
>
> OK, so it says --rebuild-tree...
>
> [root@laurynas-pc ~]# reiserfsck --rebuild-tree /dev/hda6
>
> [See Output 2 below]
>
> At this point I remounted partition read-only and looked around. And
> that's it, part of my data is at lost+found, and part is gone.
> Here was a typical mount /dev/hda6 output to syslog:
> -----------------
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: found reiserfs
> format "3.6" with standard journal
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: using ordered data
> mode
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: journal params:
> device hda6, size 8192, journal first block 18, max trans len 1024, max
> batch 900, max commit age 30, max trans age 30
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: checking transaction
> log (hda6)
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: replayed 17
> transactions in 0 seconds
> Feb 13 18:04:58 laurynas-pc kernel: ReiserFS: hda6: Using r5 hash to
> sort names
> ---------------
>
> And one more line looks particularly interesting:
> ---------------
> Feb 13 18:08:05 laurynas-pc kernel: ReiserFS: hda6: warning: vs-4080:
> reiserfs_free_block: free_block (hda6:32998)[dev:blocknr]: bit already
> cleared
> ---------------
>
> Is there anything I can do to look for my other missing data?

-- 
Thanks,
Vitaly Fertman

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

Hello,

Cituojant Vitaly Fertman <vitaly@namesys.com>:

> reboot is required between repartitioning a drive and starting to use
> 
> moved/created partitions. without that the kernel may continue to
> use
> old partition table. so it would be great to recall step-by-step
> history 
> of your copings, removes, repatitionings and reboots.

Starting from the last successful cpio between old and new /home
partitions - can I assume that data was intact at this point if cpio
succeeded?

At this point the disk has, in order of physical layout: /dev/hda5
(NTFS), 4GB /dev/hda6 (no FS), 2GB /dev/hda7 (reiser).

I tried my best to reconstruct this history, but there might be some
mistakes, of course.

[root@laurynas-pc ~]# mkfs -t reiserfs /dev/hda6

# Copy data
[root@laurynas-pc ~]# mount /dev/hda7 /home.old
[root@laurynas-pc ~]# mount /dev/hda6 /home
[root@laurynas-pc ~]# cd /home.old
[root@laurynas-pc ~]# find . -depth -print0 | cpio --null -pvd /home
[root@laurynas-pc ~]# umount /dev/hda7
[root@laurynas-pc ~]# umount /dev/hda6

# Delete /dev/hda7, delete /dev/hda6 and re-create it with the
# same starting sector, but take all former /dev/hda7 space too.
[root@laurynas-pc ~]# fdisk

# Try to resize /dev/hda6
[root@laurynas-pc ~]# resizefs.reiserfs /dev/hda6 6964146K
Error: Can't resize filesystem outside the device.

# Try to resize /dev/hda6 to a value really known to fit in the 
# new partition
# ... some 6 invocations of resizefs with values ~6GB here...
[root@laurynas-pc ~]# resizefs.reiserfs /dev/hda6 +1G
Error: Can't resize filesystem outside the device.

# Remembered about reboot
[root@laurynas-pc ~]# reboot

# Size too big; missed the -f option
[root@laurynas-pc ~]# resizefs.reiserfs /dev/hda6 +3G
Error: Can't resize filesystem outside the device.

# Do the resize!
[root@laurynas-pc ~]# resizefs.reiserfs -f /dev/hda6 +3G

[root@laurynas-pc ~]# mount /dev/hda6 /home
...typical mount output, as in previous e-mail...

[root@laurynas-pc ~]# df
... partition size and free/used space reported OK...

[root@laurynas-pc ~]# reboot

There tried to login with non-root user, and the rest of the story is
in
the previous e-mail.

Here is the current partition table:

Disk /dev/hda: 120.0 GB, 120034123776 bytes
255 heads, 63 sectors/track, 14593 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1         927     7446096   83  Linux
/dev/hda2             928         978      409657+  82  Linux swap
/dev/hda3             979       14593   109362487+   f  W95 Ext'd (LBA)
/dev/hda5             979       13726   102398278+   7  HPFS/NTFS
/dev/hda6           13727       14593     6964146   83  Linux

--
Thanks,
Laurynas

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

And I have just found following syslog entries:

Feb 13 17:59:31 laurynas-pc kernel: ReiserFS: hda6: warning: vs-4080:
reiserfs_free_block: free_block (hda6:491640)[dev:blocknr]: bit already
cleared
---
The message above repeats several hundred timws with different
blocknr's.
---
Feb 13 17:59:58 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13060:
reiserfs_update_sd: stat data of object [2 12 0x0 SD] (nlink == 1) not
found (pos 0)
Feb 13 17:59:58 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13060:
reiserfs_update_sd: stat data of object [2 12 0x0 SD] (nlink == 1) not
found (pos 1)
Feb 13 17:59:58 laurynas-pc kernel: ReiserFS: hda6: warning: vs-4080:
reiserfs_free_block: free_block (hda6:32781)[dev:blocknr]: bit already
cleared
Feb 13 17:59:58 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
Feb 13 17:59:58 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13050:
reiserfs_update_sd: i/o failure occurred trying to update [2 105 0x0
SD] stat data
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13050:
reiserfs_update_sd: i/o failure occurred trying to update [2 105 0x0
SD] stat data
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13060:
reiserfs_update_sd: stat data of object [2 12 0x0 SD] (nlink == 1) not
found (pos 1)
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-13050:
reiserfs_update_sd: i/o failure occurred trying to update [2 106 0x0
SD] stat data
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5657:
reiserfs_do_truncate: i/o failure occurred trying to truncate [2 106
0xfffffffffffffff DIRECT]
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: zam-7001:
io error in reiserfs_find_entry
Feb 13 17:59:59 laurynas-pc kernel: ReiserFS: hda6: warning: vs-5150:
search_by_key: invalid format found in block 32769. Fsck?
----
The last two lines repeat many times
----
Feb 13 18:00:07 laurynas-pc kernel: ReiserFS: hda6: warning: zam-7001:
io error in reiserfs_find_entry
Feb 13 18:00:07 laurynas-pc kernel: ReiserFS: hda6: warning: clm-2100:
nesting info a different FS
Feb 13 18:08:05 laurynas-pc kernel: ReiserFS: hda6: warning: vs-4080:
reiserfs_free_block: free_block (hda6:32998)[dev:blocknr]: bit already
cleared


--
Thanks,
Laurynas

Re: Partial data loss with reiserfs3

[Vitaly Fertman]

On Monday 14 February 2005 17:40, Laurynas Biveinis wrote:
> Hello,
>
> Cituojant Vitaly Fertman <vitaly@namesys.com>:
> > reboot is required between repartitioning a drive and starting to use
> >
> > moved/created partitions. without that the kernel may continue to
> > use
> > old partition table. so it would be great to recall step-by-step
> > history
> > of your copings, removes, repatitionings and reboots.
>
> Starting from the last successful cpio between old and new /home
> partitions - can I assume that data was intact at this point if cpio
> succeeded?
>
> At this point the disk has, in order of physical layout: /dev/hda5
> (NTFS), 4GB /dev/hda6 (no FS), 2GB /dev/hda7 (reiser).
>
> I tried my best to reconstruct this history, but there might be some
> mistakes, of course.
>
> [root@laurynas-pc ~]# mkfs -t reiserfs /dev/hda6

did you shrink ntfs under win and reboot?
what happened between the last boot and mkfs? 
did you run fdisk then? did you reboot after that fdisk run?

-- 
Thanks,
Vitaly Fertman

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

Cituojant Vitaly Fertman <vitaly@namesys.com>:

> > [root@laurynas-pc ~]# mkfs -t reiserfs /dev/hda6
> 
> did you shrink ntfs under win and reboot?

NTFS was shrinked several reboots ago under Linux with
ntfsresize/fdisk.

> what happened between the last boot and mkfs? 

I do not remember well and .bash_history isn't very helpful there. It's
very likely that mkfs was the first thing after boot.

> did you run fdisk then? did you reboot after that fdisk run?

I'm not sure what does "then" mean? After "mkfs -t reiserfs /dev/hda6"?
No, I didn't run fdisk or reboot then - I copied data.

--
Thanks,
Laurynas

Re: Partial data loss with reiserfs3

[Vitaly Fertman]

On Monday 14 February 2005 19:38, Laurynas Biveinis wrote:
> Cituojant Vitaly Fertman <vitaly@namesys.com>:
> > > [root@laurynas-pc ~]# mkfs -t reiserfs /dev/hda6
> >
> > did you shrink ntfs under win and reboot?
>
> NTFS was shrinked several reboots ago under Linux with
> ntfsresize/fdisk.
>
> > what happened between the last boot and mkfs?
>
> I do not remember well and .bash_history isn't very helpful there. It's
> very likely that mkfs was the first thing after boot.
>
> > did you run fdisk then? did you reboot after that fdisk run?
>
> I'm not sure what does "then" mean? After "mkfs -t reiserfs /dev/hda6"?
> No, I didn't run fdisk or reboot then - I copied data.

then meant before. ok, if you did not run fdisk between boot and 
mkreiserfs, then mount, copy, umount were probably fine.

after that you run fidsk -- have you run 'reiserfsck --rebuild-sb' after fdisk? 
actually resize.reiserfs does not touch data on expand at all, it just writes
bitmap blocks to the added part.

what does 
	debugreiserfs /dev/hda6
say?

what version of reiserfsprogs do you use?

-- 
Thanks,
Vitaly Fertman

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

Cituojant Vitaly Fertman <vitaly@namesys.com>:

Hello,

> then meant before. ok, if you did not run fdisk between boot and 
> mkreiserfs, then mount, copy, umount were probably fine.

It is possible that I had created, copied, destroyed partitions since
last boot - but no repartitioning.

> after that you run fidsk -- have you run 'reiserfsck --rebuild-sb'
> after fdisk? 

I've never run 'reiserfsck --rebuild-sb'.

> what does 
> 	debugreiserfs /dev/hda6
> say?

[root@laurynas-pc ~]# debugreiserfs /dev/hda6
debugreiserfs 3.6.18 (2003 www.namesys.com)


Filesystem state: consistent

Reiserfs super block in block 16 on 0x306 of format 3.6 with standard
journal
Count of blocks on the device: 1741036
Number of bitmaps: 54
Blocksize: 4096
Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
blocks):1696533
Root block: 8212
Filesystem marked as cleanly umounted
Tree height: 3
Hash function used to sort names: "r5"
Objectid map size 78, max 972
Journal parameters:
        Device [0x0]
        Magic [0x5bf05c25]
        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: 55
UUID: 11f4d25b-4b80-4dc7-8cd9-32dcd376dce4
LABEL:
Set flags in SB:
        ATTRIBUTES CLEAN


> what version of reiserfsprogs do you use?

3.6.18

--
Thanks,
Laurynas

Re: Partial data loss with reiserfs3

[Esben Stien]

Laurynas Biveinis <Laurynas.Biveinis@mif.vu.lt> writes:

> I do not remember well and .bash_history isn't very helpful
> there. It's very likely that mkfs was the first thing after boot.

Check out ttyrpld, http://ttyrpld.sf.net

-- 
Esben Stien is b0ef@esben-stien.name
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:b0ef@esben-stien.name

Re: Partial data loss with reiserfs3

[Esben Stien]

Vitaly Fertman <vitaly@namesys.com> writes:

> reboot is required between repartitioning a drive and starting to
> use moved/created partitions.

Will there ever be an end to this misery?. Is noone planning to fix this?

-- 
Esben Stien is b0ef@esben-stien.name
http://www.esben-stien.name
irc://irc.esben-stien.name/%23contact
[sip|iax]:b0ef@esben-stien.name

Re: Partial data loss with reiserfs3

[_evil]

Esben Stien wrote:
> Vitaly Fertman <vitaly@namesys.com> writes:
> 
>>reboot is required between repartitioning a drive and starting to
>>use moved/created partitions.
> 
> Will there ever be an end to this misery?. Is noone planning to fix this?

AFAIK if you partition a harddisk which is not in use (not mounted any 
of its partitions), the kernel is able to re-read the partition table 
(and says so in the syslog). that way i've created partitions on 
harddisks without rebooting.

i think [s|c]fdisk complains, if it can't re-read the table:

The partition table has been altered!
Calling ioctl() to re-read partition table.
WARNING: Re-reading the partition table failed with error 16: Device or 
resource busy.
The kernel still uses the old table.
The new table will be used at the next reboot.
Syncing disks.

Christian.

Re: Partial data loss with reiserfs3

[Simon "Sturmflut" Raffeiner]

[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]

Am Dienstag 15 Februar 2005 15:36 schrieb _evil:
> AFAIK if you partition a harddisk which is not in use (not mounted any
> of its partitions), the kernel is able to re-read the partition table
> (and says so in the syslog). that way i've created partitions on
> harddisks without rebooting.
>
> i think [s|c]fdisk complains, if it can't re-read the table:
>
> The partition table has been altered!
> Calling ioctl() to re-read partition table.
> WARNING: Re-reading the partition table failed with error 16: Device or
> resource busy.
> The kernel still uses the old table.
> The new table will be used at the next reboot.
> Syncing disks.

I think if / doesn't lie on the same hard disk it will work, at least I've 
never had to reboot a machine while partitioning unused hard drives with [c|
f]disk or parted. The ioctl() was always able to re-read the partition table.

-- 
mit freundlichen Grüßen

Simon "Sturmflut" Raffeiner

-----------------------------------
Die Weltgeschichte ist die Summe dessen, was vermeidbar gewesen wäre.
                                                   -- Oscar Wilde

GPG Public Key: 0xB2204FA0 @ hkp://subkeys.pgp.net
http://www.lieberbiber.de/pubkey.gpg

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: Partial data loss with reiserfs3

[Vitaly Fertman]

Hello,

the history with some questions. do you have anything to add here?

> I was trying to move data from my NTFS partition to Linux (Fedora Core
> 3).   I had 2GB ext3 partition for /home. After copying some files from
> NTFS partition to /home

(1) copy NTFS -> ext3

> and successfully shrinking NTFS partition by
> 4GB I wanted to enlarge my /home. 

(2) shrink NTFS

> NTFS was shrinked several reboots ago under Linux with
> ntfsresize/fdisk.

(3) reboot

> Ext3 does not support partition
> resize and move there, so I have decided to switch /home to ReiserFS
> v3 (That's the version available for FC3)
>
> At this point the disk has, in order of physical layout: /dev/hda5
> (NTFS), 4GB /dev/hda6 (no FS), 2GB /dev/hda7 (reiser).

was hda7 reiserfs or ext3 ??

> I've created 4GB Reiser partition (/dev/hda6)
> It's very likely that mkfs was the first thing after boot.

(4) create reiserfs on former NTFS, between NTFS and ext3

> and moved data there from old /home (/dev/hda7):
> umount /home
> mkdir /home.old
> mount /dev/hda7 /home.old
> mount /dev/hda6 /home
> cd /home.old
> find . -depth -print0 | cpio --null -pvd /home

(5) copy ext3 -> reiserfs

> It worked OK (as in "cpio did not fail and I could see my directories
> and files")
>
> It is possible that I had created, copied, destroyed partitions
> since last boot - but no repartitioning.

this is not clear: created, destroyed partitions means repartitioning,
changing parittion table means repartitioning. Do I understand correctly
that you mean create, copy, destroy filesystems here?

> Then I deleted my old /dev/hda7, and tried to enlarge /dev/hda6 to take
> its space - by resizing partition,

(6) fdisk: remove hda7, remove hda6, create large hda6;

> then by resizefs.reiserfs. Resizefs complained about "Error: Can't resize
> filesystem outside the device." no matter what I size I would try to expand
> it, and with '-f' option too.  It occured to me that perhaps reboot might
> be required there, so I rebooted.

(7) reboot

> Bingo, after reboot resizefs enlarged partition to the size I wanted.
>
> # Size too big; missed the -f option
> [root@laurynas-pc ~]# resizefs.reiserfs /dev/hda6 +3G
> Error: Can't resize filesystem outside the device.
>
> # Do the resize!
> [root@laurynas-pc ~]# resizefs.reiserfs -f /dev/hda6 +3G

3G just looks too large, there was only 2G hda7 as you have mentioned.
right?

(8) rezise.reiserfs

> Reboot once again

(9) reboot

> and try to login with ordinary user (whose home is on that partition).
> Login got to the point of KDE "Restoring session state" and then PC
> hanged.

(10) login failed

> Hmm. Reboot and retry login with non-root user. The same.
> Reboot and log-in as root.
>
> [root@laurynas-pc ~]# umount /home
> [root@laurynas-pc ~]# reiserfsck /dev/hda6

(11) lots of fs corruptions.
 -- some lost file StatDatas 
 -- some wrong delimiting keys
 -- some unformatted blocks are used more then once
 -- 1 formatted block is used more then once 
 -- many broken bitmap blocks

> I've never run 'reiserfsck --rebuild-sb'. progs 3.6.18
>
> debugreiserfs /dev/hda6
> Count of blocks on the device: 1741036
> Number of bitmaps: 54
> Blocksize: 4096
> Free blocks (count of blocks - used [journal, bitmaps, data, reserved]
> blocks):1696533
> Root block: 8212

when you run resizer, has it ever asked for confirmation?
like 'Do you want to continue? [y/N]:'

are you sure you have the relable memory? would you test it?

the reason of the problem is not clear. resizer on expand writes only 
to _new_ bitmap blocks and overwrites only super block, and it does 
not touch the fs storage tree.

so you can try to recover from the whole partition on the copy. Have 
you made fs/partition backup before rebuild-tree (probably fdisk)? 
If no, make a copy of the hda6 partition and run
	reiserfsck --rebuild-tree -S <hda6-copy> -l logfile
if yes, copy it back to hda6 and run on hda6.

-- 
Thanks,
Vitaly Fertman

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

Hello,

Cituojant Vitaly Fertman <vitaly@namesys.com>:

> (1) copy NTFS -> ext3
> (2) shrink NTFS
> (3) reboot

> > At this point the disk has, in order of physical layout: /dev/hda5
> > (NTFS), 4GB /dev/hda6 (no FS), 2GB /dev/hda7 (reiser).
> 
> was hda7 reiserfs or ext3 ??

Following history as you have written it, it was ext3. There were
following extra steps, that I have skipped, because at the end of them
I didn't have any problems with my data.
(3.1) create /dev/hda6 as ext3
(3.2) copy data from /dev/hda7 to /dev/hda6
(3.3) delete /dev/hda7
(3.4) find out that ext3 move/resize is unsupported
(3.5) create /dev/hda7 reiser
(3.6) copy data from /dev/hda6 to /dev/hda7

At this point I had hda7 reiser.

> (4) create reiserfs on former NTFS, between NTFS and ext3
> (5) copy ext3 -> reiserfs

> > It is possible that I had created, copied, destroyed partitions
> > since last boot - but no repartitioning.
> 
> this is not clear: created, destroyed partitions means
> repartitioning,
> changing parittion table means repartitioning. Do I understand
> correctly
> that you mean create, copy, destroy filesystems here?

Right, I meant filesystems, not partitions. Sorry.

> (6) fdisk: remove hda7, remove hda6, create large hda6;
> (7) reboot

> > [root@laurynas-pc ~]# resizefs.reiserfs -f /dev/hda6 +3G
> 
> 3G just looks too large, there was only 2G hda7 as you have
> mentioned.
> right?

Right. I have specified a value knowingly too big together with '-f'
option so that fs is resized to the maximum possible size (which is
about, but not exactly, 2G). 

> (8) rezise.reiserfs
> (9) reboot
> (10) login failed
> (11) lots of fs corruptions.
>  -- some lost file StatDatas 
>  -- some wrong delimiting keys
>  -- some unformatted blocks are used more then once
>  -- 1 formatted block is used more then once 
>  -- many broken bitmap blocks
> 
> when you run resizer, has it ever asked for confirmation?
> like 'Do you want to continue? [y/N]:'

I do not remember well, but I think there wasn't any serious warning.
If
there was a warning like "You specified +3G, I can resize only to +2G,
continue?" or similar, then I had accepted it. I would have stopped on
any more serious warning or warning that I do not understand well.

> are you sure you have the relable memory? would you test it?

The system generally is stable and GCC, being the notorious RAM
checker,
compilations do not SIGSEGV. I think I will arrange memcheck86 run to
be sure.

> the reason of the problem is not clear. resizer on expand writes only
> 
> to _new_ bitmap blocks and overwrites only super block, and it does 
> not touch the fs storage tree.
> 
> so you can try to recover from the whole partition on the copy. Have
> 
> you made fs/partition backup before rebuild-tree (probably fdisk)? 
> If no, make a copy of the hda6 partition and run
> 	reiserfsck --rebuild-tree -S <hda6-copy> -l logfile
> if yes, copy it back to hda6 and run on hda6.

I don't partition backup before rebuild-tree. I'll make one now, but it
will take some time, as free space is not readily available. I'll reply
later with results.

--
Thanks,
Laurynas

Re: Partial data loss with reiserfs3

[Laurynas Biveinis]

Hello,

Cituojant Vitaly Fertman <vitaly@namesys.com>:
> so you can try to recover from the whole partition on the copy. Have
> 
> you made fs/partition backup before rebuild-tree (probably fdisk)? 
> If no, make a copy of the hda6 partition and run
> 	reiserfsck --rebuild-tree -S <hda6-copy> -l logfile
> if yes, copy it back to hda6 and run on hda6.

Thanks a lot, it did help! All of the important files are here and
readable and according to 'df' about as much disk space is taken as was
before data loss. Of course, directory tree is broken and file names
are lost, as recovered data is in lost+found.

Below is the output and recovery log.

The question is, what has caused such behaviour in the first place? I'm
still not done with NTFS shrinking - /home expansion, but I'm afraid to
continue without understanding what went wrong here. 

Is it important to update reiserfsprogs 3.6.18 -> 3.6.19 ?

[root@laurynas-pc ~]# dd if=/dev/hda6 | bzip2 -vv > ~/partition.hda6.bz2

[root@laurynas-pc ~]# reiserfsck --rebuild-tree -S /dev/hda6 -l
recovery-from-whole-partition.log
reiserfsck 3.6.18 (2003 www.namesys.com)

*************************************************************
** Do not  run  the  program  with  --rebuild-tree  unless **
** something is broken and MAKE A BACKUP  before using it. **
** If you have bad sectors on a drive  it is usually a bad **
** idea to continue using it. Then you probably should get **
** a working hard drive, copy the file system from the bad **
** drive  to the good one -- dd_rescue is  a good tool for **
** that -- and only then run this program.                 **
** 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 rebuild the filesystem (/dev/hda6) tree
Will put log info to 'recovery-from-whole-partition.log'

Do you want to run this program?[N/Yes] (note need to type Yes if you
do):Yes
Replaying journal..
Reiserfs journal '/dev/hda6' in blocks [18..8211]: 0 transactions
replayed
###########
reiserfsck --rebuild-tree started at Thu Feb 17 10:48:43 2005
###########

Pass 0:
The whole partition (1741036 blocks) is to be scanned
Skipping 8264 blocks (super block, journal, bitmaps) 1732772 blocks will
be read
0%....20%....40%....60%....80%....100%                        left 0,
2799 /sec
        "r5" hash is selected
Flushing..finished
        Read blocks (but not data blocks) 1732772
                Leaves among those 1126
                        - leaves all contents of which could not be
saved and deleted 5
                Objectids found 4330

Pass 1 (will try to insert 1121 leaves):
Looking for allocable blocks .. finished
0%....20%....40%....60%....80%....100%                         left 0,
224 /sec
Flushing..finished
        1121 leaves read
                886 inserted
                235 not inserted
        non-unique pointers in indirect items (zeroed) 3

Pass 2:
0%....20%....40%....60%....80%....100%                         left 0,
470 /sec
Flushing..finished
        Leaves inserted item by item 235
Pass 3 (semantic):
Flushing..finished
        Files found: 4
        Directories found: 5
        Symlinks found: 1
Pass 3a (looking for lost dir/files):
Looking for lost directories:
Looking for lost files:
Flushing..finishede 0, 0 /sec
        Objects without names 149
        Empty lost dirs removed 60
        Dirs linked to /lost+found: 64
                Dirs without stat data found 1
        Files linked to /lost+found 85
Pass 4 - finished       done 0, 0 /sec
        Deleted unreachable items 60
Flushing..finished
Syncing..finished
###########
reiserfsck finished at Thu Feb 17 10:59:18 2005
###########
-------------
recovery-from-whole-partition.log:
-------------
[root@laurynas-pc ~]# cat recovery-from-whole-partition.log
####### Pass 0 #######
verify_direntry: block 8211, item 2 4336 0x0 SD (0), len 44, location
4052 entry count 65535, fsck need 0, format new: Key's offset [2 4336
0x0 SD (0)] must match the directory's hash (33204) - changed.
pass0: vpf-10180: block 32978: item 1: The item [2 12 0x1 IND (1)],
which follows non StatData item [2 6 0x1 DRCT (2)], is deleted
pass0: vpf-10180: block 32978: item 1: The item [2 112 0x1 IND (1)],
which follows non StatData item [2 6 0x1 DRCT (2)], isdeleted
block 236567: The free space (38917) is incorrect, should be (4072) -
corrected
block 266176: The free space (38917) is incorrect, should be (4072) -
corrected
block 548172: The free space (38917) is incorrect, should be (4072) -
corrected
block 578290: The free space (38917) is incorrect, should be (4072) -
corrected
block 1410673: The number of items (2560) is incorrect, should be (1) -
corrected
block 1410673: The free space (2) is incorrect, should be (2512) -
corrected
pass0: vpf-10110: block 1410673, item (0): Unknown item type found
[201331327 167772161 0x2 ??? (15)] - deleted
4273 directory entries were hashed with "r5" hash.
####### Pass 1 #######
vpf-10610: StatData item [2 4336 0x81b4 SD (0)] has non zero offset
found.
is_leaf_bad: block 8211, item 0: The corrupted item found (2 4336 0x81b4
SD (0), len 44, location 4052 entry count 65535, fsck need 0, format
new)
is_leaf_bad: WARNING: The leaf (8211) is formatted badly. Will be
handled on the the pass2.
####### Pass 2 #######
vpf-10610: StatData item [2 4336 0x81b4 SD (0)] has non zero offset
found.
####### Pass 3 #########
vpf-10680: The file [2 6] has the wrong block count in the StatData (0)
- corrected to (8)
vpf-10680: The directory [2 4335] has the wrong block count in the
StatData (8) - corrected to (1)
vpf-10650: The directory [2 4335] has the wrong size in the StatData
(3960) - corrected to (48)
####### Pass 3a (lost+found pass) #########
get_next_directory_item: The entry ".." of the directory [2 18] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 32] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 34] pointes
to [2 4], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [2 12] ("IconPositionsBRYR1a.new") in
directory [2 105] points to nowhere - is removed
vpf-10650: The directory [2 105] has the wrong size in the StatData
(160) - corrected to (120)
vpf-10680: The file [2 112] has the wrong block count in the StatData
(672) - corrected to (0)
get_next_directory_item: The entry ".." of the directory [2 296] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 308] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 323] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 638] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 656] pointes
to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 804] pointes
to [2 4], instead of [2 4335] - corrected
vpf-10680: The file [2 818] has the wrong block count in the StatData
(16) - corrected to (8)
get_next_directory_item: The entry ".." of the directory [2 1018]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 1023]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 1029]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 1033]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 1429]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2 1434]
pointes to [2 4], instead of [2 4335] - corrected
vpf-10680: The file [1438 1682] has the wrong block count in the
StatData (16) - corrected to (8)
rebuild_semantic_pass: The entry [1438 1686] ("Cache.Trash") in
directory [2 1438] points to nowhere - is removed
get_next_directory_item: The entry ".." of the directory [1438 1689]
pointes to [2 4335], instead of [2 1438] - corrected
vpf-10650: The directory [2 1438] has the wrong size in the StatData
(992) - corrected to (960)
get_next_directory_item: The entry ".." of the directory [4 1741]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1743]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1747]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1769]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1772]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1795]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1815]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1818]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1824]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1828]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1836]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1841]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1845]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1940]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 1945]
pointes to [2 4], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [2041 2053] ("Templates.sbd") in
directory [4 2041] points to nowhere - is removed
rebuild_semantic_pass: The entry [2041 2055] ("Sent.sbd") in directory
[4 2041] points to nowhere - is removed
rebuild_semantic_pass: The entry [2041 2059] ("Drafts.sbd") in directory
[4 2041] points to nowhere - is removed
rebuild_semantic_pass: The entry [2041 2061] ("Trash.sbd") in directory
[4 2041] points to nowhere - is removed
vpf-10650: The directory [4 2041] has the wrong size in the StatData
(672) - corrected to (552)
get_next_directory_item: The entry ".." of the directory [1953 2063]
pointes to [2 4335], instead of [4 1953] - corrected
vpf-10680: The file [2069 2137] has the wrong block count in the
StatData (2320) - corrected to (42816)
vpf-10680: The file [2063 2215] has the wrong block count in the
StatData (7120) - corrected to (215672)
get_next_directory_item: The entry ".." of the directory [1953 2231]
pointes to [2 4335], instead of [4 1953] - corrected
vpf-10680: The file [1949 2316] has the wrong block count in the
StatData (3712) - corrected to (72)
get_next_directory_item: The entry ".." of the directory [1949 2319]
pointes to [2 4335], instead of [4 1949] - corrected
get_next_directory_item: The entry ".." of the directory [1949 2333]
pointes to [2 4335], instead of [4 1949] - corrected
get_next_directory_item: The entry ".." of the directory [1949 2363]
pointes to [2 4335], instead of [4 1949] - corrected
get_next_directory_item: The entry ".." of the directory [4 2371]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3647]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3655]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3723]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3725]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3728]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3728 3729]
pointes to [2 4335], instead of [4 3728] - corrected
get_next_directory_item: The entry ".." of the directory [4 3767]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3777]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3777 3778]
pointes to [2 4335], instead of [4 3777] - corrected
rebuild_semantic_pass: The entry [3777 3806] ("mime-info") in directory
[4 3777] points to nowhere - is removed
get_next_directory_item: The entry ".." of the directory [3777 3807]
pointes to [2 4335], instead of [4 3777] - corrected
vpf-10650: The directory [4 3777] has the wrong size in the StatData
(152) - corrected to (120)
get_next_directory_item: The entry ".." of the directory [4 3811]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3811 3812]
pointes to [2 4335], instead of [4 3811] - corrected
get_next_directory_item: The entry ".." of the directory [4 3885]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 3894]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3894 3895]
pointes to [2 4335], instead of [4 3894] - corrected
get_next_directory_item: The entry ".." of the directory [3894 3984]
pointes to [2 4335], instead of [4 3894] - corrected
rebuild_semantic_pass: The entry [3999 4000] ("addin") in directory
[3894 3999] points to nowhere - is removed
vpf-10650: The directory [3894 3999] has the wrong size in the StatData
(72) - corrected to (48)
get_next_directory_item: The entry ".." of the directory [4 4004]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 4006]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 4230]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 4243]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4 4245]
pointes to [2 4], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [4246 4247]
pointes to [2 4335], instead of [4245 4246] - corrected
vpf-10680: The directory [4246 4255] has the wrong block count in the
StatData (1) - corrected to (2)
vpf-10650: The directory [4246 4255] has the wrong size in the StatData
(48) - corrected to (560)
get_next_directory_item: The entry ".." of the directory [4307 4308]
pointes to [2 4335], instead of [4245 4307] - corrected
get_next_directory_item: The entry ".." of the directory [4307 4313]
pointes to [2 4335], instead of [4245 4307] - corrected
get_next_directory_item: The entry ".." of the directory [4307 4318]
pointes to [2 4335], instead of [4245 4307] - corrected
get_next_directory_item: The entry ".." of the directory [4307 4321]
pointes to [2 4335], instead of [4245 4307] - corrected
rebuild_semantic_pass: The entry [4307 4323] ("wcprops") in directory
[4245 4307] points to nowhere - is removed
vpf-10650: The directory [4245 4307] has the wrong size in the StatData
(296) - corrected to (272)
get_next_directory_item: The entry ".." of the directory [4 4328]
pointes to [2 4], instead of [2 4335] - corrected
vpf-10680: The file [4328 4329] has the wrong block count in the
StatData (2544) - corrected to (13208)
get_next_directory_item: The entry ".." of the directory [1438 1691]
pointes to [1438 1689], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2069 2149]
pointes to [2069 2101], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2069 2170]
pointes to [2069 2092], instead of [2 4335] - corrected
vpf-10680: The file [2170 2179] has the wrong block count in the
StatData (6568) - corrected to (2920)
rebuild_semantic_pass: The entry [2170 2181] ("CVS.sbd") in directory
[2170 2178] points to nowhere - is removed
rebuild_semantic_pass: The entry [2170 2185] ("Users.sbd") in directory
[2170 2178] points to nowhere - is removed
rebuild_semantic_pass: The entry [2170 2187] ("Workers.sbd") in
directory [2170 2178] points to nowhere - is removed
vpf-10650: The directory [2170 2178] has the wrong size in the StatData
(296) - corrected to (208)
get_next_directory_item: The entry ".." of the directory [2170 2189]
pointes to [2 4335], instead of [2069 2170] - corrected
rebuild_semantic_pass: The entry [2170 2198] ("SourceForge.sbd") in
directory [2069 2170] points to nowhere - is removed
get_next_directory_item: The entry ".." of the directory [2170 2201]
pointes to [2 4335], instead of [2069 2170] - corrected
rebuild_semantic_pass: The entry [2170 2207] ("GPC Announcements.sbd")
in directory [2069 2170] points to nowhere - is removed
rebuild_semantic_pass: The entry [2170 2209] ("Mozilla Bugzilla.sbd") in
directory [2069 2170] points to nowhere - is removed
vpf-10650: The directory [2069 2170] has the wrong size in the StatData
(736) - corrected to (624)
get_next_directory_item: The entry ".." of the directory [2231 2237]
pointes to [1953 2231], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2231 2263]
pointes to [1953 2231], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2231 2278]
pointes to [1953 2231], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2231 2294]
pointes to [1953 2231], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [2231 2305]
pointes to [1953 2231], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3811 3828]
pointes to [3811 3812], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3897]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3900]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3909]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3914]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3919]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3939]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3942]
pointes to [3894 3895], instead of [2 4335] - corrected
get_next_directory_item: The entry ".." of the directory [3942 3943]
pointes to [2 4335], instead of [3895 3942] - corrected
get_next_directory_item: The entry ".." of the directory [3942 3954]
pointes to [2 4335], instead of [3895 3942] - corrected
get_next_directory_item: The entry ".." of the directory [3895 3978]
pointes to [3894 3895], instead of [2 4335] - corrected
rebuild_semantic_pass: The entry [3978 3980] ("fontmetric") in directory
[3895 3978] points to nowhere - is removed
rebuild_semantic_pass: The entry [3978 3981] ("driver") in directory
[3895 3978] points to nowhere - is removed
vpf-10650: The directory [3895 3978] has the wrong size in the StatData
(136) - corrected to (80)
vpf-10680: The file [2069 2071] has the wrong block count in the
StatData (1448) - corrected to (1296)

--
Thanks,
Laurynas