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: <1162691856.21654.61.camel@localhost.localdomain>
Date:	Sun, 05 Nov 2006 01:57:35 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Albert Cahalan <acahalan@...il.com>
Cc:	kangur@...com.net, mikulas@...ax.karlin.mff.cuni.cz,
	linux-kernel@...r.kernel.org
Subject: Re: New filesystem for Linux

Ar Sad, 2006-11-04 am 14:59 -0500, ysgrifennodd Albert Cahalan:
> New drives will soon use 4096-byte sectors. This is a better
> match for the normal (non-VAX!) page size and reduces overhead.

The innards of the disk are already a file system in themselves. The
disk is a network storage appliance on a funny cable with an odd command
set, nothing else. The internal storage model of the drive and external
one can be quite different.

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

Also theoretically states like "random block you only read in the middle
of moving".

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

It happens because
-	There is limited if any protection on the PCI bus generally
-	Many PC systems don't have ECC memory, ECC cache
-	PATA does not CRC protect the command block so if you do enough PATA
I/O (eg you are a US national lab ..) you *will* eventually get a bit
flip that gives you the wrong sector with no error data. SATA fixes that
one.
-	Murphy is out to get you..

Network people use end to end checksums, when working with huge data
sets people generally use app<->app checksums. Serious network using
people with big data sets also often turn off the hardware checksum
support on network cards - its faster but riskier.

> 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

Not seen that, although they do move stuff aorund in their internal
block management of bad blocks. I've also seen hardware errors that lead
to data being messed up silently. 

Alan

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