$ ls /boot/config*
/boot/config-2.6.18-6-amd64 /boot/config-2.6.29-2-amd64
/boot/config-2.6.26-1-amd64 /boot/config-2.6.30-1-amd64
$ grep LBD /boot/config*
/boot/config-2.6.18-6-amd64:CONFIG_LBD=y
Is it at all concerning that the sd driver tries a read capacity 16 and fails?
I propose the following sequence of events:
1) 'sd' block device tries to read capacity 16 and fails because CONFIG_LBD is not asserted, defaulting to a size of 2TB
2) 'hfsplus' then tries to mount this larger-than-2TB filesystem and is successful
3) Writes to this inappropriately mounted filesystem fail once they run off of the edge
I submit that the proposed patch is in error, and that hfsplus does very well support >2TB filesystems on Linux. Further, hfsplus and all filesystem drivers should check for the degenerate case of block device < filesystem size. This is probably good practice anyhow, as filesystem corruption can manifest itself so.
Dan Dennison