NetBSD-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Two scenarios leading to filesystem corruption under NetBSD-4.0, anyone seen this?

        Hello.  I'm not sure if this is a related issue or not.  I'm not
seeing filesystem corruption in the sense that fsck doesn't pass the
filesystem after a change.  What I'm seeing is that the files on the
filesystem do not contain the data which they're supposed to.  this applies
to both MSDOS and FFS filesystems connected via USB.  In the MSDOS case, I
can get the corect results by not having two processes write to the
filesystem at once.


On Apr 15, 11:16am, "Greg A. Woods; Planix, Inc." wrote:
} Subject: Re: Two scenarios leading to filesystem corruption under NetBSD-4
} On 15-Apr-08, at 2:40 AM, Brian Buhrow wrote:
} >     Hello.  I'm running NetBSD-4.0-stable on several systems, and I've
} > noticed two scenarios where files can become incredibly corrupt,  
} > perhaps
} > they're related, perhaps not, I'm not sure.
} >     Has anyone else run into these problems, and, if so, did you have a
} > fix, or maybe shed some light on the trouble?
} Indeed!  I've found that I can easily trash an MS-DOS floppy image  
} (connected with vnd(4) and mounted with mount_msdos(8)) just by adding  
} or removing a file from it.  This can be easily confirmed with  
} fsck_msdos(8).
} -- 
}                                       Greg A. Woods; Planix, Inc.
}                                       <>
>-- End of excerpt from "Greg A. Woods; Planix, Inc."

Home | Main Index | Thread Index | Old Index