Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*4K\s+drives\,\s+sectsz\=512\,\s+bsize\=4096\s*$/: 12 ]

Total 12 documents matching your query.

1. 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 30 Aug 2010 09:56:16 +0200
I have 2x 2TB 4K sector drives, joined with LVM to RAID-0. On top of that, I created an XFS, but that has sectsz=512. Will there be any real difference if I re-format with sectsz=4096? AFAIK, XFS wil
/archives/xfs/2010-08/msg00304.html (7,447 bytes)

2. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 31 Aug 2010 23:01:34 +0200
Nobody? Is my assumption correct that a change in sectsz from 512 to 4096 would be of no difference for the filesystem? -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet
/archives/xfs/2010-08/msg00329.html (8,908 bytes)

3. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 31 Aug 2010 16:16:49 -0500
Just be sure your first sector of your top-level block device is 4k aligned, and then yes you'll want to set sector size to 4k so that xfs will do all log IO in 4k blocks as well. If you do it right
/archives/xfs/2010-08/msg00330.html (8,523 bytes)

4. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 00:07:20 +0200
I can only hope LVM does it right, I have no idea how it aligns. And that's what's interesting me: why? Won't XFS do all I/Os at minimum for a given block size? Or is it possible XFS does write only
/archives/xfs/2010-08/msg00331.html (9,680 bytes)

5. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 31 Aug 2010 17:15:29 -0500
the log can do things on sector size boundaries. I don't think so ... -Eric
/archives/xfs/2010-08/msg00332.html (9,151 bytes)

6. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 1 Sep 2010 08:34:28 +1000 (EST)
Log I/O and direct writes are sector sized & aligned. There's no way (other than dump, mkfs & restore), the filesystem is laid out differently (most data structures, like superblocks and other metada
/archives/xfs/2010-08/msg00333.html (8,411 bytes)

7. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 01:12:37 +0200
Great, thanks to both of you for clarification. Going to reformat now... -- mit freundlichen Grüssen, Michael Monnerie, Ing. BSc it-management Internet Services http://proteger.at [gesprochen: Prot-
/archives/xfs/2010-08/msg00335.html (8,775 bytes)

8. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Gim Leong Chin <chingimleong@xxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 13:35:10 +0800 (SGT)
Hi, I would like to know how the inode size should be configured for 4 kB sector drives? Should we leave it at the default 256 bytes, or set it to the maximum of 2 kB? Do inodes occupy discrete secto
/archives/xfs/2010-09/msg00000.html (10,194 bytes)

9. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Nathan Scott <nathans@xxxxxxxxxx>
Date: Wed, 1 Sep 2010 15:59:42 +1000 (EST)
There is no direct correlation between inode size and sector size. See above. Keep the defaults unless you have a good reason not to. They occupy part of a filesystem block. cheers. -- Nathan
/archives/xfs/2010-09/msg00001.html (7,784 bytes)

10. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 09:38:46 +0200
An interesting question. Why are inodes sizes configurable at all? To store ACLs? How would one know when bigger Inodes should be used? And what is the implication when they would be needed but aren
/archives/xfs/2010-09/msg00003.html (8,759 bytes)

11. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 06:24:12 -0400
As nathan mentioned XFS issues log I/O based on the sector size, and we do allow direct I/O down to the sector size. That's two reasons why or why you don't want a 4096 byte sector size. Depending on
/archives/xfs/2010-09/msg00009.html (8,855 bytes)

12. Re: 4K drives, sectsz=512, bsize=4096 (score: 1)
Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 1 Sep 2010 06:13:36 -0400
The XFS inode consists of three parts: - the fixed format dinode - the data fork - the attribute fork the fixed format inode is fixed size, so any change in the inode size only applies to the data an
/archives/xfs/2010-09/msg00011.html (9,713 bytes)


This search system is powered by Namazu