Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
We have a logical drive (raid 1+0) enabled with 210 GB and is formatted with ReiserFS. Recently, we got an error which is given below: ReiserFS: cciss/c0d1p1: warning: vs-13060: reiserfs_update_sd: stat data of object [8210 8809 0x0 SD] (nlink == 1) not found (pos 1)
and we lost almost 75 GB of freespace.
So we did reiserfsck --check [device] and it suggested to use --rebuild-tree.
Doing reiserfsck --rebuild-tree [device] corrected the error and we regained the lost space. Now, since --rebuild-tree covers only data blocks (blocks only with data), we thought of checking the complete partition. Hence we used,
This started scanning and after PASS 2, it has given a message:
Quote:
vpf-10260: The file we are inserting the new item (2 8280 0x17a1b8001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17a5ac001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17a9a0001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17ad94001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17b188001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17b57c001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17b970001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17bd64001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17c158001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17c54c001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17c940001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17cd34001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x17d128001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
vpf-10260: The file we are inserting the new item (2 8280 0x170001 IND (1), len 4048, location 48 entry count 0, fsck need 0, format new) into has no StatData, insertion was skipped
left 82, 73 /sec
Its now 2.5 hours and there is no progress (no message in console). I am not in a position to kill this process, as killing reiserfsck during --rebuild-tree will make the device unmountable to prevent further data corruption.
I checked the ps aux|grep reiserfsck using a different console, then I came to know, that it is using a significant amount of CPU. I just wanted to make sure, that this is quite normal and its running in the background and is not in a state where it isn't working. Please do suggest some tips. Thanks in advance. Thank you.
My advice is when it's finished to stop using Reiserfs. You're lucky if it doesn't cause problems. I remember reading something once about how under certain circumstances ext2 would work fine, and reiserfs would corrupt data, and the reiser people claimed that it was a hardware issue, not a problem with the filesystem. Anyway I've had a couple of nasty situations dealing with reiserfs (and so have plenty of others) that I don't think it's worth the risk.
I am extremely sorry for the very late reply. The problem got fixed. I didn't have to do anything. But it took very long time (more than 1.5 days) to completely scan the whole hard drive. The system responded and rebuilt the tree structure. We regained the lost partition space. Thank you.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
