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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.63.0611022346450.14187@alpha.polcom.net>
Date:	Thu, 2 Nov 2006 23:54:17 +0100 (CET)
From:	Grzegorz Kulewski <kangur@...com.net>
To:	Mikulas Patocka <mikulas@...ax.karlin.mff.cuni.cz>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

Hi,

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."

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?


Thanks,

Grzegorz Kulewski

-
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/