Carlos E. R. wrote:
On 2015-01-09 09:29, auxsvr@gmail.com wrote:
On Thursday 08 of January 2015 15:52:17 Carlos E. R. wrote:
I've observed the core issue with two USB to SATA adaptors.
That's a terrible one.
(thread "What is a recommended XFS sector size for hybrid (512e) advanced format hard drives?") === It's not just USB adapters. Had an LSI-SAS+SATA RAID card, NEW, a few years back. It didn't recognize the 4KB sector size and reported the devices as having 512-byte sectors (which worked fine if you had all your alignment ducks in a row).
I could format things to 4k, but was a bit paranoid about some FS-layer (partitioner, lvm, mkfs) storing some extra data, "somewhere", such that it might throw off the alignment. At least with 1M partition boundaries and mostly defaults on lvm, mkfs.xfs does allow specifying the 'real' hardware sector size (regardless of what the OS thinks it is -- assuming the real is >= and a multiple of the kernel's idea). Upgrading the card semi-solved the problem -- at least the kernel see the 4096 byte sectors in one place, but other places: Ishtar:/sys/dev/block/8:0/queue> disp_files_w_recursion.sh |grep -P 'sector_size|block_|io_size' hw_sector_size : 512 logical_block_size : 512 minimum_io_size : 4096 optimal_io_size : 0 physical_block_size : 4096 --- It's a bit curious that the 'optimal_io_size' is '0'... does that mean optimally you shouldn't perform i/o on it? ;-) ---- Main thing to watch out for w/32 bit is NOT to enable 64-bit inodes. Once enabled, you can't easily go back -- and I believe it was thought that 32-bit machines could "do" w/32 bits, and if you needed more, then you'd need to move to a 64-bit machine. Not sure if that is still the case, but something to be aware of (and test for if you need it)... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org