also sprach dean gaudet [EMAIL PROTECTED] [2006.11.03.2019 +0100]:
I cannot find authoritative information about the relation between
the RAID chunk size and the correct stride parameter to use when
creating an ext2/3 filesystem.
you know, it's interesting -- mkfs.xfs somehow gets the
Shaya Potter wrote:
[please cc: me on responses]
if one read Documentation/fs/ntfs.txt in the linux kernel, it talks
about accessing windows raid volumes in Linux
If one is using non raid-5, one can use the device mapper, but if one is
using raid-5, one has to use the md driver.
However, it
Hi,
I'm setting up a raid 5 system and I ran across a bug when reshaping an
array with a mounted XFS filesystem on it. This is under linux 2.6.18.2
and mdadm 2.5.5
I have a test array with 3 10 GB disks and a fourth 10 GB spare disk,
and a mounted xfs filesystem on it:
[EMAIL PROTECTED]
i think i've got my mdadm.conf set properly for an external bitmap -- but
it doesn't seem to work. i can assemble from the command-line fine
though:
# grep md4 /etc/mdadm/mdadm.conf
ARRAY /dev/md4 bitmap=/bitmap.md4 UUID=dbc3be0b:b5853930:a02e038c:13ba8cdc
# mdadm -A /dev/md4
mdadm: Could not
On Sat, 4 Nov 2006, martin f krafft wrote:
also sprach dean gaudet [EMAIL PROTECTED] [2006.11.03.2019 +0100]:
I cannot find authoritative information about the relation between
the RAID chunk size and the correct stride parameter to use when
creating an ext2/3 filesystem.
you know,
Hi everyone,
I recently got an email warning from Zabbix about my raid array, so I
went to have a look at it:
--
Personalities : [linear] [raid0] [raid1] [raid10] [raid5] [raid4]
md2 : active raid5 hdk1[3] hdi1[2] hdg1[1] hde1[0]
1172126208 blocks level 5, 32k chunk, algorithm 2
