On Sun, 28 Nov 2010 04:18:25 + Ben Hutchings b...@debian.org wrote:
On Sun, 2010-11-28 at 08:28 +1100, Neil Brown wrote:
The fix I would recommend for 2.6.26 is to add
if (q-merge_bvec_fn)
rs-max_phys_segments = 1;
to dm_set_device_limits. Though the redhat one
On Mon, 29 Nov 2010 00:08:47 + Ben Hutchings b...@debian.org wrote:
if (q-merge_bvec_fn !ti-type-merge)
limits-max_segments = 1;
(the test on -type-merge is important and applies to 2.6.26 as well).
Why is it not necessary to set seg_boundary_mask to
On Sat, 27 Nov 2010 19:53:54 + Ben Hutchings b...@debian.org wrote:
Neil, would you mind looking at this:
On Sat, 2010-11-27 at 10:49 +0100, Wouter D'Haeseleer wrote:
Ben,
I'm running 4 days now without any disk errors anymore.
As stated in my previous message this is with the
On Thu, 25 Feb 2010 08:16:14 +0100
Goswin von Brederlow goswin-...@web.de wrote:
Neil Brown ne...@suse.de writes:
On Wed, 24 Feb 2010 14:41:16 +0100
Goswin von Brederlow goswin-...@web.de wrote:
Neil Brown ne...@suse.de writes:
On Tue, 23 Feb 2010 07:27:00 +0100
martin f
On Wed, 24 Feb 2010 18:52:57 +0100
Mario 'BitKoenig' Holbe mario.ho...@tu-ilmenau.de wrote:
On Wed, Feb 24, 2010 at 02:13:53PM +0100, Goswin von Brederlow wrote:
grub.cfg (grub2) uses UUID for grub itself. But the kernel can be bootet
with root=/dev/md0. But in that case where does it get
On Wed, 24 Feb 2010 14:41:16 +0100
Goswin von Brederlow goswin-...@web.de wrote:
Neil Brown ne...@suse.de writes:
On Tue, 23 Feb 2010 07:27:00 +0100
martin f krafft madd...@madduck.net wrote:
The only issue homehost protects against, I think, is machines that
use /dev/md0 directly from
On Tue, 23 Feb 2010 07:27:00 +0100
martin f krafft madd...@madduck.net wrote:
also sprach Neil Brown ne...@suse.de [2010.02.23.0330 +0100]:
The problem to protect against is any consequence of rearranging
devices while the host is off, including attaching devices that
previously were
On Mon, 22 Feb 2010 10:16:32 +0100
martin f krafft madd...@madduck.net wrote:
also sprach Piergiorgio Sartor piergiorgio.sar...@nexgo.de [2010.02.21.2113
+0100]:
I do not see how the homehost plays a role, here.
Neil,
Could you please put forth the argument for why the homehost must
On Monday October 15, [EMAIL PROTECTED] wrote:
seems as the size is the same?
seems.
I was hoping for
cat /proc/partitions
and maybe even
fdisk -l /dev/hda /dev/hdb
I should have been more specific.
NeilBrown
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of
As you say, the devices are exactly the same size, thanks.
On Monday October 15, [EMAIL PROTECTED] wrote:
how do I undo? mdadm /dev/md2 -f /dev/hda2
So I could try the sync in init 1
Lucas
Well, you could:
mdadm /dev/md2 -f /dev/hda2
mdadm /dev/md2 -r /dev/hda2
then when you are
On Monday October 8, [EMAIL PROTECTED] wrote:
reassign 445573 linux-image-2.6.18-5-686
tags 445573 patch confirmed
severity 445573 minor
thanks
also sprach Neil Brown [EMAIL PROTECTED] [2007.10.08.0231 +0100]:
Yep, this is a kernel bug.
This should fix it.
Can you provide an ETA
On Thursday January 11, [EMAIL PROTECTED] wrote:
Thanks for the report, and the patch. Has the raid1 recovery fix been
submitted upstream yet?
I've sent it to Andrew Morton. I suspect it will be in 2.6.20
I'll be sending it to -stable later today.
NeilBrown
--
To UNSUBSCRIBE, email to
12 matches
Mail list logo
