On Mon, Mar 31, 2003 at 12:00:14PM +0400, Oleg Drokin wrote:
> > http://www.orbis-terrarum.net/~robbat2/reiserfs/debugreiserfs.run
> "bread: Cannot read the block (18)."
> Well, now this is something.
> Do you have I/O errors messages in kernel logs, or do you know another reason for
> it to fail reading 18th block?
Nope, no I/O messages in the logs at all.

> Perhaps try to run "badblocks -b 4096" to find out if there are more blocks
> that cannot be read?
I had previously scanned the partition only, but I've scanned the entire
drive now, just to be entirely certain, and there are no bad blocks at
all. I've tested with both the standard readonly test, and the
non-destructive read/write.

The drive is a FUJITSU MPC3102AT-E, one of the ones without the firmware
issues (these drives pre-Feb 2001 had a firmware bug).

> We accept money too ;)
I'll keep that in mind then.

> > A question for you, so I can support things. Is there a list somewhere
> > of features requested, and how much you money you want to be paid to add
> > them in? Especially the smaller features (hint hint).
> Well, there is http://namesys.com/support.html , as of features, usually
> we expect customers to come up with features they need. If you lack something
> in reiserfs and you are willing to pay, we can implement it.
> If you are happy with the current features-set, why to pay for features that
> would be never used?
I've been trying and using reiserfs since before it was officially in
2.4, and this is actually the first real issue I've hit with it. I had
just wondered if you had some feature list of minor things you would
like, but never had time for. Eg nice to have, but not crucial.
Random thing I saw while reading ReiserFS docs, like maybe the repacker?
But I suspect that may be a much larger task (and I certianly don't want
my drives and RAID arrays ever getting that full in the first place).

-- 
Robin Hugh Johnson
E-Mail     : [EMAIL PROTECTED]
Home Page  : http://www.orbis-terrarum.net/?l=people.robbat2
ICQ#       : 30269588 or 41961639
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to