Pedro Martelletto wrote:
It should be of no surprise that if you don't step up and report an
issue, it won't get fixed.

As I did not know if it was an issue or if I had done something stupid myself, I never filed a report. I have never claimed I did so. I was wondering what hosed my filesystem, and tedu confirmed that msdosfs very well could be the bad guy. If I were to file a report, it would be more step-by-step and, at best, even repeatable.

That said, let's get on what actually matters:

Yup.

Alexander, can you please try to build a test-case that rules out NFS,
if at all possible? It certainly looks like the culprit.

Would that mean no NFS at all on the computer, both mounts and exports, or would it be sufficient with no NFS concerning the msdos partition and the sharing thereof?

Also, are you
still running 3.7, or have you tried a more recent version of OpenBSD?

At the time I was running 3.7 on one computer and 3.6 on the other. Since a few days ago, 3.6 is no more since I upgraded to an available snapshot (Sep 2 02:40). That would be on my laptop, where (if I recall correctly) the problems last appeared.

If you have, were you still able to reproduce the same problems?

No, but as I now mount msdos r/o, I would be surprised if I would have been. :d

Finally, please don't say you have cool diffs to make things work, and
that if people want to do X or Y under OpenBSD, they should go talk to
you. Submit them for review. This is not Linux.

Ah, well, they are not diffs. They are more like quick-and-dirty .c programs that scan the disk for things that look like avi's and/or .jpg's. I get what you mean, but I'm simply not THAT proud of them, and I don't think they will contribute much to this list.

Anyway, I am in a position quite like Frantisek, i.e. where my wish is _not_ to repeat the problem, since I like to keep my images and data intact. What I _could_ do is to free up some space for a new partition and try to reproduce the problems there. msdosfs should not be able to fsck something up outside of its wdXX now, should it? The coming week/weeks I will be quite occupied, but as this is an issue I would like to have solved, I hope to be able to produce some decent problem reports later on.

/Alexander

Reply via email to