4 ms·
fact that Microsoft is implementing it in the kernel should still be a huge help If you're trying to recover video (which is one of the easiest types of data
by userbinator 7y ago
fact that Microsoft is implementing it in the kernel should still be a huge help
If you're trying to recover video (which is one of the easiest types of data to recover, due to it being large, sequentially written, and bitstreams containing easily recognisable sync markers), and especially from a storage device that's being exclusively used for video, the actual filesystem doesn't really matter because practically all of the sane ones will store the file data in a contiguous range of blocks. Depending on the exact codec, you may even be able to dd the raw device into a decoder and it'll simply find the first valid sync marker and start decoding from there.
- dkh 7y agoWell of course, some file carving is what has gotten me out of a few messes in the past, including the one mentioned. But in a situation where a volume won't mount/read, it's nice to eliminate a poor implementation or FUSE issue as a potential variable in determining if there's actually a problem. (Or worse, introducing a new problem... I've seen that, too, especially in earlier days of exfat-fuse/exfat-utils.)