On Saturday 08 January 2005 03:44, hanasaki wrote:
Could you outline exactly what takes place on a rebuild-tree?
reiserfs has two types of blocks. There are unformatted nodes. They
contain plain user file data. And there are formatted nodes. These may
contain both user file data and filesystem
On Tuesday 04 January 2005 20:25, hanasaki wrote:
Version of reiserfsk
==
== From debian sarge
/sbin/reiserfsck -V
reiserfsck 3.6.19 (2003 www.namesys.com)
== also used the version in knoppix 3.7 with similar results
the output of two consecutive runs of --rebuild-tree
Could you outline exactly what takes place on a rebuild-tree?
I was under the incorrect assumption that if a rebuild-tree is 100%
successful then the FS is ok and a subsequent rebuild-tree will have
nothing to fix/report. .
Vitaly Fertman wrote:
On Tuesday 04 January 2005 20:25, hanasaki
Hello
On Sun, 2005-01-02 at 00:55, hanasaki wrote:
Running reiser3 on kernel 2.6.10 and 2.6.9 with Debian sarge and unstable.
the --rebuild-tree always finds errors and corrects them. even when run
more than once consecutively without mounting the partition in between.
Please provide
Version of reiserfsk
==
== From debian sarge
/sbin/reiserfsck -V
reiserfsck 3.6.19 (2003 www.namesys.com)
== also used the version in knoppix 3.7 with similar results
the output of two consecutive runs of --rebuild-tree on the same
unmounted partition are attached. Below is
Hello
On Tue, 2005-01-04 at 20:25, hanasaki wrote:
Version of reiserfsk
==
== From debian sarge
/sbin/reiserfsck -V
reiserfsck 3.6.19 (2003 www.namesys.com)
== also used the version in knoppix 3.7 with similar results
the output of two consecutive runs of
Running reiser3 on kernel 2.6.10 and 2.6.9 with Debian sarge and unstable.
the --rebuild-tree always finds errors and corrects them. even when run
more than once consecutively without mounting the partition in between.
--check says all is good.
Running reiser3 on kernel 2.6.10 and 2.6.9 with Debian sarge and unstable.
the --rebuild-tree always finds errors and corrects them. even when run
more than once consecutively without mounting the partition in between.
--check says all is good.
