linux-ext4 - Re: problem(?) in ext4 or mke2fs

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: <4D98C2E0.3010808@redhat.com>
Date:	Sun, 03 Apr 2011 11:56:32 -0700
From:	Eric Sandeen <sandeen@...hat.com>
To:	Zeev Tarantov <zeev.tarantov@...il.com>
CC:	linux-ext4@...r.kernel.org
Subject: Re: problem(?) in ext4 or mke2fs

On 4/3/11 11:52 AM, Zeev Tarantov wrote:
> On Sun, Apr 3, 2011 at 21:40, Eric Sandeen <sandeen@...hat.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html