Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+mount\s+failuer\s+on\s+RAID5\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*XFS\s+mount\s+failuer\s+on\s+RAID5\s*$/: 10 ]

Total 10 documents matching your query.

1. XFS mount failuer on RAID5 (score: 1): Author: hank peng <pengxihan@xxxxxxxxx>; Date: Fri, 16 Oct 2009 11:09:27 +0800; Hi, all: I have a self-built board, cpu is MPC8548(PPC arch), kernel is based on MPC8548CDS demo board, version is 2.6.23. A SATA controller is conected to CPU via PCIX, and I have 3 disks attached t; /archives/xfs/2009-10/msg00156.html (10,865 bytes)
2. Re: XFS mount failuer on RAID5 (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Fri, 16 Oct 2009 10:19:09 +0200; You can set the *sector* size to 4k only when your drives have 4k sector size. Normal disks so far always have 512 Bytes/sector. mfg zmi -- // Michael Monnerie, Ing.BSc -- http://it-management.at //; /archives/xfs/2009-10/msg00158.html (7,977 bytes)
3. Re: XFS mount failuer on RAID5 (score: 1): Author: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>; Date: Fri, 16 Oct 2009 04:30:26 -0400 (EDT); Hi, 2.6.23.. can you retry with 2.6.32-rcX or 2.6.31 to see if you can reproduce the problem? Justin. Hi, all: I have a self-built board, cpu is MPC8548(PPC arch), kernel is based on MPC8548CDS demo; /archives/xfs/2009-10/msg00159.html (11,481 bytes)
4. Re: XFS mount failuer on RAID5 (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 16 Oct 2009 10:27:13 -0500; You can set the *sector* size to 4k only when your drives have 4k sector size. Normal disks so far always have 512 Bytes/sector. mfg zmi Actually -ssize=4k is just fine even on 512 sector disks. -Eri; /archives/xfs/2009-10/msg00161.html (8,332 bytes)
5. Re: XFS mount failuer on RAID5 (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 16 Oct 2009 10:28:40 -0500; hank peng wrote: Hi, all: I have a self-built board, cpu is MPC8548(PPC arch), kernel is based on MPC8548CDS demo board, version is 2.6.23. A SATA controller is conected to CPU via PCIX, and I have 3; /archives/xfs/2009-10/msg00162.html (9,412 bytes)
6. Re: XFS mount failuer on RAID5 (score: 1): Author: Eric Sandeen <sandeen@xxxxxxxxxxx>; Date: Fri, 16 Oct 2009 10:55:13 -0500; Eric Sandeen wrote: hank peng wrote: Hi, all: I have a self-built board, cpu is MPC8548(PPC arch), kernel is based on MPC8548CDS demo board, version is 2.6.23. A SATA controller is conected to CPU vi; /archives/xfs/2009-10/msg00163.html (9,967 bytes)
7. Re: XFS mount failuer on RAID5 (score: 1): Author: Michael Monnerie <michael.monnerie@xxxxxxxxxxxxxxxxxxx>; Date: Sat, 17 Oct 2009 23:27:04 +0200; Oh funny. So what's the meaning of this argument then? Or why would one set it to 4k? What's the diff with 512b? mfg zmi -- // Michael Monnerie, Ing.BSc -- http://it-management.at // Tel: 0660 / 415; /archives/xfs/2009-10/msg00164.html (8,616 bytes)
8. Re: XFS mount failuer on RAID5 (score: 1): Author: hank peng <pengxihan@xxxxxxxxx>; Date: Mon, 19 Oct 2009 08:54:35 +0800; 2009/10/16 Eric Sandeen <sandeen@xxxxxxxxxxx>: Reason is found, it is because there are some problem in our hardware XOR driver firmware. I am sure now it is not related with XFS. Thx to all you guys; /archives/xfs/2009-10/msg00169.html (11,982 bytes)
9. Re: XFS mount failuer on RAID5 (score: 1): Author: Dave Chinner <david@xxxxxxxxxxxxx>; Date: Mon, 19 Oct 2009 12:30:18 +1100; A hardware sector is the atomic unit of IO. 4k sectors on 512b hardware sectors means that a single 4k filesystem sector write is not necessarily atomic. This can lead to problems with torn writes at; /archives/xfs/2009-10/msg00172.html (9,644 bytes)
10. Re: XFS mount failuer on RAID5 (score: 1): Author: Christoph Hellwig <hch@xxxxxxxxxxxxx>; Date: Sun, 18 Oct 2009 23:55:38 -0400; This should not happen anymore with 2.6 series kernels.; /archives/xfs/2009-10/msg00176.html (9,224 bytes)

Current List: 1 - 10
Page: [1]