I'm trying to add a new SAN LUN to a system, create a multipath mdadm
device on it, partition it, and create a new filesystem on it, all
without taking the system down.
All goes well, up to partitioning the md device:
# fdisk /dev/md12
Device contains neither a valid DOS partition table,
Guess hdparm -z /dev/md12 would do the trick, if you're lucky enough...
2006/5/30, Herta Van den Eynde [EMAIL PROTECTED]:
I'm trying to add a new SAN LUN to a system, create a multipath mdadm
device on it, partition it, and create a new filesystem on it, all
without taking the system down.
All
Did I miss an answer to this? As the weather gets hotter I'm doing all I
can to reduce heat.
Marc L. de Bruin wrote:
Lo,
Situation: /dev/md0, type raid1, containing 2 active devices
(/dev/hda1 and /dev/hdc1) and 2 spare devices (/dev/hde1 and /dev/hdg1).
Those two spare 'partitions' are
Neil Brown wrote:
On Friday May 26, [EMAIL PROTECTED] wrote:
On Tue, May 23, 2006 at 08:39:26AM +1000, Neil Brown wrote:
Presumably you have a 'DEVICE' line in mdadm.conf too? What is it.
My first guess is that it isn't listing /dev/sdd? somehow.
Neil,
i am seeing a lot of
Hello,
I am trying to create a RAID5 array out of 3 160GB SATA drives. After
i create the array i want to partition the device into 2 partitions.
The system lies on a SCSI disk and the 2 partitions will be used for
data storage.
The SATA host is an HPT374 device with drivers compiled in the
On Tue, May 30, 2006 at 01:10:24PM -0400, Bill Davidsen wrote:
2) deprecate the DEVICE keyword issuing a warning when it is found in
the configuration file
Not sure I'm so keen on that, at least not in the near term.
Let's not start warning and depreciating powerful features because they
can
On Tue, May 30, 2006 at 03:59:33PM +0200, Herta Van den Eynde wrote:
I'm trying to add a new SAN LUN to a system, create a multipath mdadm
device on it, partition it, and create a new filesystem on it, all
without taking the system down.
All goes well, up to partitioning the md device:
#
2006/5/30, Luca Berra [EMAIL PROTECTED]:
Guess hdparm -z /dev/md12 would do the trick, if you're lucky enough...
please avoid
top posting
quoting full emails
give advice if you are not sure
Sorry for my ugly-looking short answer...
I shall say for my own defense (if the President of the Court
On 5/30/06, Luca Berra [EMAIL PROTECTED] wrote:
On Tue, May 30, 2006 at 08:08:03PM +0300, Michael Theodoulou wrote:
Hello,
I am trying to create a RAID5 array out of 3 160GB SATA drives. After
i create the array i want to partition the device into 2 partitions.
The system lies on a SCSI disk
On Tuesday May 30, [EMAIL PROTECTED] wrote:
Hello,
I am trying to create a RAID5 array out of 3 160GB SATA drives. After
i create the array i want to partition the device into 2 partitions.
The system lies on a SCSI disk and the 2 partitions will be used for
data storage.
The SATA host
On Tuesday May 30, [EMAIL PROTECTED] wrote:
On Tue, 30 May 2006, Neil Brown wrote:
Could you try this patch please? On top of the rest.
And if it doesn't fail in a couple of days, tell me how regularly the
message
kblockd_schedule_work failed
gets printed.
i'm running this
On Tuesday May 30, [EMAIL PROTECTED] wrote:
actually i think the rate is higher... i'm not sure why, but klogd doesn't
seem to keep up with it:
[EMAIL PROTECTED]:~# grep -c kblockd_schedule_work /var/log/messages
31
[EMAIL PROTECTED]:~# dmesg | grep -c kblockd_schedule_work
8192
# grep
On Wed, 31 May 2006, Neil Brown wrote:
On Tuesday May 30, [EMAIL PROTECTED] wrote:
actually i think the rate is higher... i'm not sure why, but klogd doesn't
seem to keep up with it:
[EMAIL PROTECTED]:~# grep -c kblockd_schedule_work /var/log/messages
31
[EMAIL PROTECTED]:~#
13 matches
Mail list logo
