linux-kernel - Re: New filesystem for Linux

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 4 Nov 2006 14:59:53 -0500
From:	"Albert Cahalan" <acahalan@...il.com>
To:	kangur@...com.net, mikulas@...ax.karlin.mff.cuni.cz,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

Re: New filesystem for Linux

kangur@...com.net, mikulas@...ax.karlin.mff.cuni.cz,
linux-kernel@...r.kernel.org

Grzegorz Kulewski writes:
> On Thu, 2 Nov 2006, Mikulas Patocka wrote:
>> As my PhD thesis, I am designing and writing a filesystem,
>> and it's now in a state that it can be released. You can
>> download it from http://artax.karlin.mff.cuni.cz/~mikulas/spadfs/
>
> "Disk that can atomically write one sector (512 bytes) so that
> the sector contains either old or new content in case of crash."

New drives will soon use 4096-byte sectors. This is a better
match for the normal (non-VAX!) page size and reduces overhead.

> Well, maybe I am completly wrong but as far as I understand no
> disk currently will provide such requirement. Disks can have
> (after halted write):
> - old data,
> - new data,
> - nothing (unreadable sector - result of not full write and disk
> internal checksum failute for that sector, happens especially
> often if you have frequent power outages).
>
> And possibly some broken drives may also return you something that
> they think is good data but really is not (shouldn't happen since
> both disks and cables should be protected by checksums, but hey...
> you can never be absolutely sure especially on very big storages).
>
> So... isn't this making your filesystem a little flawed in design?

It's equal to typical modern designs like JFS, NTFS, XFS, and Reiserfs.

It's much worse than ZFS, which doesn't even trust the filesystem
to not silently scramble the data.

It's a tad worse than various forms of ext2/ext3/ufs/ufs2, where a
fixed layout helps recovery. (ext2 lacks the atomic updates, but
it doesn't trust a bad shutdown either -- fsck will always run)

BTW, a person with disk recovery experience told me that drives
will sometimes reorder the sectors. Sector 42 becomes sector 7732,
sector 880880 becomes sector 12345, etc. The very best filesystems
can handle with without data loss. (for example, ZFS) Merely great
filesystems will at least recognize that the data has been trashed.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/