Another data point: I can't remember ever when NTFS didn't come up clean
after a crash, except of course when the disk itself was bad.


"NTFS (NT File System) is a proprietary journaling file system developed by
Microsoft. Starting with Windows NT 3.1, it is the default file system of
the Windows NT family."


On Mon, Aug 24, 2020 at 7:41 AM David Brownlee <[email protected]> wrote:

> On Mon, 24 Aug 2020 at 11:46, Mouse <[email protected]> wrote:
> >
> > > I think the general consensus is that ffs can be inconsistent it ways
> > > fsck is unable to detect.
> >
> > ...much less fix.  Yes.  When I was doing the program that eventually
> > got massaged into resize_ffs, during development I had some filesystems
> > that were definitely corrupted but that fsck was happy with.  (I rather
> > wish I'd saved some of them as test cases, but I didn't.)
>
> Sounds like there is an in interesting fuzzing project in there for
> someone - make a filesystem mage and the repeatedly damage it, then
> see if fsck can fix it, then if you get a rump panic when moving
> everything around, and then re-run fsck to see if it indicates any new
> issues :)
>
> (So far 3.5TB of my original RAID1 filesystem transferred to a plain
> disk, so should be able to run some A/B fsck tests later today to
> establish if the raid controller is the issue in this case)
>
> David
>
>
> David
>

Reply via email to