Matthew Wilcox wrote:
On Tue, Mar 25, 2008 at 10:31:54AM -0400, Ric Wheeler wrote:
I think that there are many embedded applications (lots of them linux based)
which have large amounts of storage behind low power, low cost 32 bit CPU's.
Think of the home/small office NAS boxes that you can get from bestbuy or
other big box stores. Those devices today have 4 S-ATA drives (each of
which can be 1TB in size).
Also, if you have a very low end box, it can still access really large
storage
over iSCSI or a SAN which will present as a local, large device.
Don't those devices run into trouble with fsck? The amount of memory
you need to fsck a device is obviously going to depend on the filesystem,
but it has to grow with device size, and I'm not sure that 4GB is enough
virtual address space to fsck 2TB.
Absolutely - they more or less hit a stonewall once the disk has any trouble and
you need to fsck. On the other hand, this might be merciful since on 64 bit
boxes, we will let you run the fsck and watch it run for a week or so before you
despair ;-)
On a serious note, fsck time tends to track more the number of active inodes, so
you can fsck a large file system if you use it to store large files (especially
if you use a file system with dynamic inode creation or something like the
uninitialized ext4 inodes).
ric
--
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
