Re: problem(?) in ext4 or mke2fs

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Cheers, Andreas

On 2011-04-03, at 8:56 AM, Eric Sandeen <sandeen@xxxxxxxxxx> wrote:

> On 4/3/11 11:52 AM, Zeev Tarantov wrote:
>> On Sun, Apr 3, 2011 at 21:40, Eric Sandeen <sandeen@xxxxxxxxxx> wrote:
> 
> ...
> 
>>> What does
>>> 
>>> # blockdev --getiomin --getioopt /dev/<yourdevice>
>>> 
>>> say for your device?
>> 
>> get logical block (sector) size: 4096
>> get physical block (sector) size: 4096
>> get minimum I/O size: 4096
>> get optimal I/O size: 4096
>> get alignment offset in bytes: 0
>> get max sectors per request: 255
>> get blocksize: 4096
>> get readahead: 256
>> 
>>> The device may be reporting odd values, but mke2fs probably
>>> should be smart enough not to set block-sized stripe unit and width...
>> 
>> If the filesystem created with the default options is slow or has
>> higher cpu usage, it should be changed.
> 
> I agree.  For actual striped storage, this makes it faster, but this
> case is a problem; block-sized stripe width is never going to be good.
> What device is this, exactly?
> 
> -Eric (losing my free airport wifi in about 8 minutes, so I may have
> to continue this later...!)
> 
>>> -Eric
>> 
>> -Z.T.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Reiser Filesystem Development]     [Ceph FS]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite National Park]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]     [Linux Media]

  Powered by Linux