On 8 May 2007, Michael Tokarev told this:
BTW, for such recovery purposes, I use initrd (initramfs really, but
does not matter) with a normal (but tiny) set of commands inside,
thanks to busybox. So everything can be done without any help from
external recovery CD. Very handy at times,
On Tuesday May 8, [EMAIL PROTECTED] wrote:
Neil, awesome patch-- what are the chances of it getting merged into
2.6.22?
Probably. I want to think it through a bit more - to make sure I can
write a coherent and correct changelog entry.
NeilBrown
-
To unsubscribe from this list: send the
Nix wrote:
On 8 May 2007, Michael Tokarev told this:
BTW, for such recovery purposes, I use initrd (initramfs really, but
does not matter) with a normal (but tiny) set of commands inside,
thanks to busybox. So everything can be done without any help from
external recovery CD. Very handy at
Benjamin Schieder wrote:
[EMAIL PROTECTED]:~# mdadm /dev/md/2 -r /dev/hdh5
mdadm: hot remove failed for /dev/hdh5: No such device
md1 and md2 are supposed to be raid5 arrays.
You are probably using udev, don't you? Somehow there's presently
no /dev/hdh5, but to remove /dev/hdh5 out of the
Hi,
we are presently running into a hotplug/linux-raid problem.
Lets assume a hard disk entirely fails or a stupid human being pulls it out of
the system. Several partitions of the very same hardisk are also part of
linux-software raid. Also, /dev is managed by udev.
Problem-1) When the disk
Hi
The resync numbers you sent, looks very promising :)
Do you have any performance numbers that you can share for these set of
patches, which shows the Rd/Wr IO bandwidth.
Thanks
Ronen Shitrit
-
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to
also sprach Bernd Schubert [EMAIL PROTECTED] [2007.05.09.1417 +0200]:
Problem-1) When the disk fails, udev will remove it from /dev. Unfortunately
this will make it impossible to remove the disk or its partitions
from /dev/mdX device, since mdadm tries to read the device fail and will
abort
http://kerneltrap.org/node/8176
I am a mdadm/disk/hard drive fanatic, I was curious:
On i386, we can at most fit 256 scatterlist elements into a page,
and on x86-64 we are stuck with 128. So that puts us somewhere
between 512kb and 1024kb for a single IO.
How come 32bit is 256 and 64 is only
On Wednesday 09 May 2007 15:14:50 martin f krafft wrote:
also sprach Bernd Schubert [EMAIL PROTECTED] [2007.05.09.1417 +0200]:
Problem-1) When the disk fails, udev will remove it from /dev.
Unfortunately this will make it impossible to remove the disk or its
partitions from /dev/mdX device,
On Wed, May 09 2007, Justin Piszcz wrote:
http://kerneltrap.org/node/8176
Oh
I am a mdadm/disk/hard drive fanatic, I was curious:
On i386, we can at most fit 256 scatterlist elements into a page,
and on x86-64 we are stuck with 128. So that puts us somewhere
between 512kb and 1024kb for a
On 9 May 2007, Michael Tokarev spake thusly:
Nix wrote:
On 8 May 2007, Michael Tokarev told this:
BTW, for such recovery purposes, I use initrd (initramfs really, but
does not matter) with a normal (but tiny) set of commands inside,
thanks to busybox. So everything can be done without any
Bernd Schubert wrote:
Benjamin Schieder wrote:
[EMAIL PROTECTED]:~# mdadm /dev/md/2 -r /dev/hdh5
mdadm: hot remove failed for /dev/hdh5: No such device
md1 and md2 are supposed to be raid5 arrays.
You are probably using udev, don't you? Somehow there's presently
no /dev/hdh5, but to
Bernd Schubert wrote:
Hi,
we are presently running into a hotplug/linux-raid problem.
Lets assume a hard disk entirely fails or a stupid human being pulls it out
of
the system. Several partitions of the very same hardisk are also part of
linux-software raid. Also, /dev is managed by
Hi Linus,
Could you please revert
5b479c91da90eef605f851508744bfe8269591a0
It causes an oops when auto-detecting raid arrays, and it doesn't seem
easy to fix.
The array may not be 'open' when do_md_run is called, so bdev-bd_disk
might be NULL, so bd_set_size can oops.
I cannot really open
On Thu, 10 May 2007, Neil Brown wrote:
Hi Linus,
Could you please revert
5b479c91da90eef605f851508744bfe8269591a0
Done.
(But Andrew never saw your email, I suspect: [EMAIL PROTECTED] is probably
some strange mixup of Andrew Morton and Andi Kleen in your mind ;)
On 10.05.2007 01:23:27, Michael Tokarev wrote:
Bernd Schubert wrote:
Benjamin Schieder wrote:
[EMAIL PROTECTED]:~# mdadm /dev/md/2 -r /dev/hdh5
mdadm: hot remove failed for /dev/hdh5: No such device
md1 and md2 are supposed to be raid5 arrays.
You are probably using udev,
16 matches
Mail list logo
