On Monday May 23, [EMAIL PROTECTED] wrote:
>
> tags 274859 +patch
> thanks
>
> [martin f krafft]
> > I checked out the source and opening is not hard... but mdadm also
> > creates device nodes and uses S_ISBLK all over the place, so I don't
> > really know whether adding a "|| S_ISLNK" will fix i
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 [EMA
On Saturday December 16, [EMAIL PROTECTED] wrote:
>
> Don't use the Debian/GNU 3.1 with software RAID1 and kernel 2.6.18.
> I tested with SCSI and IDE drives with different controllers and PCs
> and IMPORTANT DATA LOSS can occur. It seems to be a problem with mdadm,
> maybe a new version of mdadm
On Thursday December 14, [EMAIL PROTECTED] wrote:
> On Mon, Nov 20, 2006 at 05:20:34PM -0500, J. Bruce Fields wrote:
> > No modification required if we remove it from upstream too. Do people
> > use it?
>
> It seems like nobody does, judging from the response. Is there any chance of
> a relativel
On Thursday November 2, [EMAIL PROTECTED] wrote:
>
> Neil, can we apply the patch contributed to fix this:
>
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi/mdadm-fix-infinite-loop.diff?bug=396582;msg=5;att=1
>
> or do I remember that you previously replaced devlist with NULL to
> fix anothe
Package: libc6
Version: 2.3.6.ds1-13
Severity: normal
Tags: patch
On 64bit machines, svc_getreqset ignores filedescriptors 32-63 and others.
This has been fixed in glibc 2.4 but needs to be
fixed in 2.3.6.debian while we keep using it.
The consequence of this bug is that if mountd (or any other r
On Tuesday April 3, [EMAIL PROTECTED] wrote:
> Hi,
>
> I've got a bugreport [0] from a user trying to use raid and uswsusp. He's
> using initramfs-tools available in debian. I'll describe the problem
> and my analysis, maybe you can comment on what you think. A warning: I only
> have a casual unde
Package: slapd
Version: 2.3.27-1
Severity: normal
Compiling slapd with SLAPI support would make it a lot easier to
develop, test, and use SLAPI plugins :-)
Thanks
NeilBrown
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architectur
On Thursday October 12, [EMAIL PROTECTED] wrote:
>
> That's for sure :) Do you know if it could impact stability of the
> packages? I do not really want to risk anything as the packages
> should get ready for the release soon...
I haven't done a thorough review of the code, but from what I have
On Thursday August 10, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.5.3-1~unreleased.3
> Severity: normal
>
> Dear Neil,
>
> Here's an issue I've stumbled over today: say /etc/mdadm/mdadm.conf
> refers to /dev/md1, but that does not exist during boot and udev
> does *not* create it. Now
--
Send online/offline uevents when an md array starts/stops.
This allows udev to do something intellegent when an
array becomes available.
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c |2 ++
1 file changed, 2 insertions(+)
diff .prev/drive
On Sat, 27 Nov 2010 19:53:54 + Ben Hutchings 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 RedHat
On Sun, 28 Nov 2010 04:18:25 + Ben Hutchings 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
On Mon, 29 Nov 2010 00:08:47 + Ben Hutchings 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 PAGE_C
Package: git-daemon-run
Version: 1:1.7.6.3-1
Severity: normal
Dear Maintainer,
sometimes an incoming connection the the git-daemon will abort in such
a way that the daemon doesn't notice and keeps the connection open.
When git is upgraded the daemon will be killed and restarted. When it
On Sunday May 6, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.5.6-9
>
> I don't know whether this is a bug, but here's what happened.
> I had two mirrors operational /dev/hd[ac]1 and /dev/hd[ac]3 on md0 and md1,
> respectively.
> On Apr 23, /dev/hdc started to complain about bad sectors
On Wednesday May 9, [EMAIL PROTECTED] wrote:
>
> Neil Brown <[EMAIL PROTECTED]> [2007.04.02.0953 +0200]:
> >Hmmm... this is somewhat awkward. You could argue that udev should be
> >taught to remove the device from the array before removing the device
> >from /dev.
On Thursday May 10, [EMAIL PROTECTED] wrote:
> Neil Brown wrote:
> > On Wednesday May 9, [EMAIL PROTECTED] wrote:
> >> Neil Brown <[EMAIL PROTECTED]> [2007.04.02.0953 +0200]:
> >>> Hmmm... this is somewhat awkward. You could argue that udev should be
> &
On Thursday May 10, [EMAIL PROTECTED] wrote:
>
> No, I haven't, but it is getting near the top of my list.
I have just committed a change to the mdadm .git so that
mdadm /dev/md4 --fail detached
will fail any components of /dev/md4 that appear to be detached (open
returns -ENXIO). and
mdad
Package: latex2html
Version: 2002-2-1-20050114-5
Severity: normal
Tags: patch
latex2html seems to expect framebox to take two options (square bracket)
arguments before the
main argument.
Infact it takes a (), a [] and then the {}.
This patch fixes it for me.
--- /usr/bin/latex2html.orig20
I believe this bug is fixed by
http://neil.brown.name/git?p=mdadm;a=commitdiff;h=60b435db5a7b085ad1204168879037bf14ebd6d1
see below.
NeilBrown
From: Chris Webb <[EMAIL PROTECTED]>
Date: Thu, 19 Jun 2008 06:30:39 + (+1000)
Subject: Fix bug in forced assemble.
X-Git-Tag: mdadm-3.0-devel1~
On Wednesday August 20, [EMAIL PROTECTED] wrote:
>
> The current Debian sid kernel 2.6.26-2 does sync the disks if I add
> them.
> I tried now even the newer 2.6.27-rc3-git6 out, because it has a few MD
> changes.
> That one adds the disks only as `spare' but does not start a resync.
I cannot rep
On Saturday September 27, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.6.7-3.1
> Severity: important
> Tags: upstream
>
> md0 : active raid1 hda1[1]
> 64220 blocks super 1.0 [2/1] [_U]
>
> wall:/# sfdisk -s /dev/hdc1
> 64228
>
> wall:/# mdadm --add /dev/md0 /dev/hdc1
> mdadm: /de
On Monday January 5, kirkl...@canonical.com wrote:
> On Fri, 2008-12-19 at 16:02 +1100, Neil Brown wrote:
> > I'm not really keen on taking this sort of patch.
> > It isn't clear that an abort (caused by the assert) is really much
> > better than just segfaulting n
.6.7.1.
I include it below.
NeilBrown
>From 56f8add211a840faaed325bd16483b55da544e93 Mon Sep 17 00:00:00 2001
From: Neil Brown <[EMAIL PROTECTED]>
Date: Thu, 19 Jun 2008 16:30:36 +1000
Subject: [PATCH] Fix an error when assembling arrays that are in the middle of
a reshape.
It is important
This bug is a kernel bug rather than an mdadm bug.
It is almost certainly the bug fixed by
commit 9744197c3d7b329590c2be33ad7b17409bd798fe
which went into 2.6.27.
Nothing is actually going wrong. It is just an annoying message.
If it bothers you, run the command
echo 0 > /proc/sys/kernel/
I'm not really keen on taking this sort of patch.
It isn't clear that an abort (caused by the assert) is really much
better than just segfaulting normally ... though you do get a message
I guess.
But it makes the code rather ugly.
Maybe if you defined a asprintf_nofail (possibly an inline in mdad
On Wednesday June 28, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.5.2-1
> Severity: important
>
> If rootfs is on LVM, which in turn is on RAID, the mdadm hook
> determines that RAID is not needed:
>
> ++ df /
> ++ sed -ne 's,^\(/dev/[^[:space:]]\+\).*,\1,p'
> + ROOTRAIDDEV=/dev/
Package: cupsys
Version: 1.2.1-2
Severity: grave
Justification: renders package unusable
Cupsd crashes occasionally, particularly when browing the web interface.
I compiled from src and ran 'gdb' on the version with all the symbols
still intact, and the problem is near line 2541 on scheduler/dir
sumption grows up to around 50% running
> /sbin/mdadm --monitor --pid-file /var/run/mdadm.pid --mail root
> --daemonise --scan
>
Yeah, thanks...
See patch.
NeilBrown
Fix memory leak in monitor mode
When rescanning /dev, we didn't free the old list.
Also don't search for devic
see no reason why mdadm shouldn't exit with code 0...
Neither can I. It'll be fixed in the next release. Thanks.
NeilBrown
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./Examine.c |5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff ./Exami
On Thursday June 15, [EMAIL PROTECTED] wrote:
> tags 373802 confirmed upstream
> thanks
>
> Neil, this one's for you.. future compatibility and all that jazz.
> :)
>
> - Forwarded message from Martin Michlmayr <[EMAIL PROTECTED]> -
>
> Now it fails with the following error with GCC 4.2.
On Thursday June 1, [EMAIL PROTECTED] wrote:
> tags 369779 + confirmed upstream pending
> thanks
>
> I can confirm this bug. For now, it surely suffices to add
> -fno-strict-aliasing in Debian if you, Neil, still use the flag for
> development.
>
> I am surely not touching dlink.h, even though th
On Thursday June 1, [EMAIL PROTECTED] wrote:
> > Unfortunately, this means that you have to recreate the arrays. At
> > least I do not know of a way to migrate version-0 to version-1.
>
> Magic : a92b4efc
> Version : 00.90.00
>UUID : 881b45c3:b1f47d8a:7b9b8401:167b0d0
On Wednesday June 24, francois-xavier.russo...@cea.fr wrote:
> Package: mdadm
> Version: 2.6.7.2
> Severity: critical
>
> After booting a Debian 5.0.1 - Lenny install cdrom in rescue mode
> (debian-501-ia64-netinst.iso) on an Itanium 2 server with Debian 3.1
> - Sarge (ia64) installed on a softwar
On Wednesday October 3, [EMAIL PROTECTED] wrote:
> Hi,
>
> thanks for your report and the patch and sorry for the delay.
>
> Neil Brown wrote:
> > latex2html seems to expect framebox to take two options (square bracket)
> > arguments before the
> > main argu
.
NeilBrown
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/md.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff .prev/drivers/md/md.c ./drivers/md/md.c
--- .prev/drivers/md/md.c 2007-08-20 11:36:09.0 +1000
+++ ./drivers
Thanks for the bug report.
This is now fixed in the upstream .git by the following patch.
It highlights the fact that while you can turn on the write-mostly
bit, you cannot easily turn it off. I wonder if that is a problem.
NeilBrown
### Diffstat output
./Manage.c |8 +---
1 file ch
On Sunday September 23, [EMAIL PROTECTED] wrote:
> On Sat, Sep 22, 2007 at 10:42:31AM -0700, David Liontooth wrote:
> > Package: nfs-kernel-server
> > Version: 1:1.1.0-13
> > Severity: normal
> >
> >
> > The command to unexport a directory appears to no longer have any effect.
> >
> > I issue "e
On Thursday October 11, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.5.6-9
> Severity: normal
>
> Hello,
> I am trying to setup raid1 on my pc.
> I have 2 identical drives. 270+gb. each with 3 partitions.
> 30gb hdb1 -> md0
> 250gb hdb2 ->md2
> 4gb swap hdb5 ->md4
>
> Initially my
On Friday October 12, [EMAIL PROTECTED] wrote:
> yes I have.
> Then I tried booting in knoppix to see if maybe there are hdd problems
> so I run e2fsck on both drives to see if there are any issues.
> reboot and it still does the same thing.
Ok, it must be caused by some persistent state.
Could yo
On Monday September 24, [EMAIL PROTECTED] wrote:
>
> Hi Neil,
>
> Thanks for looking.
>
> Neil Brown wrote:
> > On Sunday September 23, [EMAIL PROTECTED] wrote:
> >
> >> On Sat, Sep 22, 2007 at 10:42:31AM -0700, David Liontooth wrote:
> >>
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.
> &
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 "unsu
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 r
On Monday August 31, robe...@debath.co.uk wrote:
> On Sun, 30 Aug 2009, martin f krafft wrote:
>
> > Why specify it in the first place? I suggest to remove all metadata=
> > stuff from mdadm.conf. Inspect the /usr/share/mdadm/mkconf output.
>
> I didn't.
>
> It got added automatically... Bug?
On Friday April 11, [EMAIL PROTECTED] wrote:
> > I have attached said patch, maybe it should be included in the
> > Debian package?
>
> Jonathan, does the patch fix things for you?
>
> Neil, the patch on
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=462154 is not
> upstream yet. Should I add
On Friday April 11, [EMAIL PROTECTED] wrote:
> tags 474548 upstream
> thanks
>
> also sprach Alex Samad <[EMAIL PROTECTED]> [2008.04.06.1525 +0200]:
> > seems like there is an error in 2.6.x stream of mdadm, when trying to
> > hot add a disk to a raid1 array after 1 disk failed.
> >
> > I tried t
On Friday April 11, [EMAIL PROTECTED] wrote:
> also sprach Wakko Warner <[EMAIL PROTECTED]> [2008.04.11.1802 +0200]:
> > That wasn't the point. The point was I wasn't able to "examine"
> > the "file". There's absolutely no reason that one has to attach it
> > to a loopback device just to examine t
Package: hal-info
Version: 20080317+git20080318-1
Severity: normal
My Dell Latitude D820 doesn't have working video after
a suspend/resume cycle.
It seems that the quirk in 20-video-quirk-pm-dell.fdi is wrong,
at least for my notebook.
It contains
true
I need
true
On Friday July 4, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.6.7-2
> Severity: minor
>
> Hi,
>
> the mdadm.conf man page does not explain the HOMEHOST setting.
True.
A future release will have this text:
HOMEHOST
The homehost line gives a default value for t
On Saturday August 2, [EMAIL PROTECTED] wrote:
> On Fri, Aug 01, 2008 at 11:15:33PM +1000, Aníbal Monsalve Salazar wrote:
> > On Mon, Jul 28, 2008 at 03:13:19AM -0400, Steve Dickson wrote:
> > >I just cut the 1.1.3 nfs-utils release. Unfortunately I'm having
> > >issues accessing my kernel.org acco
On Tuesday March 4, [EMAIL PROTECTED] wrote:
> Package: mdadm
> Version: 2.6.4-1
> Followup-For: Bug #462154
>
>
> I've had it after a few creates (raid benchmarking atm) as well, and
> assembles.
>
> It seems to crash *after* what it's supposed to do, though, i. e.:
>
> segfault at 00
It looks like you are relaying on in-kernel autodetection, and sdd2
and sdd1 don't have the RAID Autodetect partition type.
I would change all the partition types to something else myself, but
it would work to change those two to be Autodetect.
NeilBrown
--
To UNSUBSCRIBE, email to [EMAIL PR
Package: vm
Version: 7.19-14
Severity: normal
When I reply to an email from someone with an 8-bit character in their name,
such as
"=?iso-8859-1?Q?V=EDctor_Paesa?=" <[EMAIL PROTECTED]>
The In-reply-to field gets the un-escaped name:
In-Reply-To: message from Víctor Paesa on Sunday July 15
Package: make
Version: 3.80+3.81.rc1-1
Severity: important
While doing kernel development (in the latest -mm tree if it makes a
difference), make always want to recompile everything since upgrading
to this version. Other packages with simpler make files work ok.
I've just down graded to 3.80+3
On Tue, 29 Jun 2010 14:24:07 -0400
Jim Paris wrote:
> My guess is that in Manage.c:Manage_subdevs, the loops like
> for (; j < array.raid_disks + array.nr_disks ; j++) {
> are missing disks because the disk numbers are changing as they are
> removed, but I didn't have the time to follow the c
On Fri, 19 Feb 2010 16:37:29 +0100
Joachim Zobel wrote:
> Do the upstream kernel developers know about this? A box unnecessarily
> taking 1h+ for a reboot is a rather serious problem.
I do now.
I'm quite surprised though. Any attempted by other programs to access the
devices should cause the r
On Mon, 22 Feb 2010 10:16:32 +0100
martin f krafft wrote:
> also sprach Piergiorgio Sartor [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
> match, and why unconditional auto-ass
On Tue, 23 Feb 2010 07:27:00 +0100
martin f krafft wrote:
> also sprach Neil Brown [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 at
On Wed, 24 Feb 2010 18:52:57 +0100
"Mario 'BitKoenig' Holbe" 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 the homehost from
> >
On Wed, 24 Feb 2010 14:41:16 +0100
Goswin von Brederlow wrote:
> Neil Brown writes:
>
> > On Tue, 23 Feb 2010 07:27:00 +0100
> > martin f krafft wrote:
> >> The only issue homehost protects against, I think, is machines that
> >> use /dev/md0 directly from
On Thu, 25 Feb 2010 08:16:14 +0100
Goswin von Brederlow wrote:
> Neil Brown writes:
>
> > On Wed, 24 Feb 2010 14:41:16 +0100
> > Goswin von Brederlow wrote:
> >
> >> Neil Brown writes:
> >>
> >> > On Tue, 23 Feb 2010 07:27:00 +0100
On Mon, 7 Jun 2010 16:25:47 +0100
Martin Michlmayr wrote:
> * martin f krafft [2010-05-26 10:31]:
> > also sprach Neil Brown [2010.05.26.1016 +0200]:
> > > The most likely explanation for this is that /var/run/mdadm/map existed
> > > and
> > > contained a
On Tue, 8 Jun 2010 12:37:38 +0200
martin f krafft wrote:
> also sprach Martin Michlmayr [2010.06.08.1124 +0200]:
> > > It would be safer to use
> > >mdadm -As
> > > to ensure all arrays are assembled, then
> > >mdadm -Ds
> > > to create mdadm.conf
> > >
> > > ... but why do you even wan
Package: gnome-panel
Version: 2.30.2-2
Severity: normal
The recent gnome-panel update to 2.30.2-2 caused the workspace
switcher to misbehave.
My configuration is for 9 workspaces in 3 rows - so 3 by 3.
This works find in 2.30.2-1 (which I have reverted back to).
In 2.30.2-2, the '3 rows' setting
On Sat, 17 Jul 2010 15:49:22 +0200
Björn Påhlsson wrote:
.
> # mdadm --verbose --grow /dev/md0 --level=raid6 --raid-devices=4
>
> The output of that last command is:
>
> mdadm level of /dev/md0 changed to raid6
> Segmentation fault
>
When I try that (thanks for providing precise commands!
On Thu, 22 Jul 2010 16:15:32 +1000
Neil Brown wrote:
> on Debian, though I'm still running 2.6.32-5-amd64. I doubt that would
> make a difference, but it might.
And if fact it does. I found a 2.6.34 kernel and hit the same bug.
The mdadm bug is fixed by upst
On Tue, 08 Jun 2010 13:25:13 +0200
"Jean-Luc Coulon (f5ibh)" wrote:
> I've a system with lvm2 over raid1 and some filesystems encrypted.
> When I updated mdadm from 3.1.1-1 to 3.1.2-1 the system failed to boot kernel
> 2.6.34 (from experimental).
> I tried 3.1.2-2 when it was released, I got the
On Thu, 22 Jul 2010 09:30:17 +0200
Jean-Luc Coulon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 22/07/2010 09:04, Neil Brown a écrit :
> >
>
> >
> > I wonder if it could be
> >commit b179246f4f519082158279b2f45e5fd51842cc42
> &
On Thu, 22 Jul 2010 12:36:47 +0200
Jean-Luc Coulon wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Le 22/07/2010 10:16, Neil Brown a écrit :
> >
> > On Thu, 22 Jul 2010 09:30:17 +0200
> > Jean-Luc Coulon wrote:
>
> [ ... ]
>
> >
On Sun, 25 Jul 2010 22:08:12 +0200
Jan Echternach wrote:
> Package: mdadm
> Version: 3.1.2-2
> Severity: normal
>
> I get an udevadm settle timeout during boot after upgrading mdadm from
> version 3.1.1-1 to 3.1.2-2:
If you are up to compiling and installing your own mdadm, could you try
revert
On Mon, 26 Jul 2010 21:37:47 +0200
Jan Echternach wrote:
> On Mon, Jul 26, 2010 at 06:44:25PM +1000, Neil Brown wrote:
> > If you are up to compiling and installing your own mdadm, could you try
> > reverting
> >
> > http://neil.brown.name
On Thu, 28 Jan 2010 08:13:46 +1300
martin f krafft wrote:
> Package: mdadm
> Version: 3.1.1-1
> Severity: serious
> Justification: no longer builds from source on certain architectures
> Tags: upstream confirmed
> Forwarded: ne...@suse.de
>
> -Wall -Werror -Wstrict-prototypes -ggdb -fomit-frame-
On Wed, 27 Jan 2010 14:13:36 +1300
martin f krafft wrote:
> also sprach RUSSOTTO François-Xavier 200103
> [2009.12.02.0407 +1300]:
> > As I suggested to Neil: prior to auto-remount a raid array, the
> > raid tool should perform a version checking so that, at least,
> > user is warned that the r
On Sunday March 1, goswin-...@web.de wrote:
> Package: mdadm
> Version: 2.6.8-12-gb47dff6-2
> Severity: wishlist
>
> Hi,
>
> just recently Ingo Juergensmann brought up a question on irc about
> converting a raid1 into a raid5. Currently --grow does not support
> that but one can achive it manualy
On Fri, 29 Jan 2010 15:44:27 -0700
Rob Sims wrote:
> Still not fixed:
> $ mdadm --remove /dev/md0 /dev/sdd1
> mdadm: /dev/md0 does not appear to be an md device
> $ mdadm --version
> mdadm - v3.1.1 - 19th November 2009
Thanks.
I have committed the following fix upstream which should resolve th
On Thu, 27 May 2010 21:51:47 +0200
martin f krafft wrote:
> Package: mdadm
> Version: 3.1.2-1
> Severity: serious
> Tags: upstream
> Justification: fails to build from source on ia64 (at least)
>
> Another one of these, which upstream will hopefully fix:
>
> gcc -Wall -Werror -Wstrict-prototype
On Fri, 19 Mar 2010 06:45:12 +0200
Jari Aalto wrote:
> Would you have any insight on this bug:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=271766
>
> Unfortunately there is no test cases to try, so it's a long shot.
Fortunately there is enough of a test-case. I found a suitable x
On Thursday January 8, kirkl...@canonical.com wrote:
> Neil-
>
> One more follow-up on this patch...
>
> I actually think that the code in the inline function should :
>
> - ret = asprintf(strp, fmt, ap);
> + ret = vasprintf(strp, fmt, ap);
>
> Otherwise, we might fill ap into the f
On Wednesday January 7, chr...@debian.org wrote:
> Package: mdadm
> Version: 2.6.7-1
> Severity: wishlist
>
> It'd nice if the help printed out when running mdadm -G --help also
> mentioned the "max" parameter that can be passed to the -z option. Just
> a one-line mention would be fine. (I know
On Wednesday February 4, madd...@debian.org wrote:
> tags 510261 confirmed upstream
> forwarded 510261 ne...@suse.de
> thanks
>
> also sprach John McMonagle [2008.12.30.2214 +0100]:
> > In both cases I rebooted before the sync was done.
> > In both cases arrays re-synced from the beginning.
> > A
On Fri, 01 Oct 2010 13:53:13 +0200
Paul Slootman wrote:
> Package: mdadm
> Version: 3.1.4-1+8efb9d1
> Severity: important
>
> I noticed that when adding internal bitmaps to md devices,
> that the chunks used were far too large:
That depends on what you mean by 'too large'.
I find that the ideal
I'm fairly sure this is a known bug which is fixed in 3.1.3 which has just
been released in Debian (I think).
The problem is that mdadm tries to use /lib/init/rw which doesn't exist
during the initramfs stage.
If you repeat your experiment with init=/bin/sh, and
mkdir -p /lib/init/rw
before s
On Mon, 30 Nov 2009 12:14:02 -0600
Manoj Srivastava wrote:
> Uday Reddy wrote:
> > I agree that this is a bug. But, if you leave the variable
> > vm-in-reply-to-format with its default value "%i" then you won't
> > have this problem.
>
> manoj
Thanks!
I had completely forgotten that
On Mon, 7 Dec 2009 18:55:24 +0100
m...@linux.it (Marco d'Itri) wrote:
> reassign 554461 mdadm
> thanks
>
> On Dec 07, Andrea Palazzi wrote:
>
> > At boot time the system (usually) complains about /dev/sdc and /dev/sdc1
> > having a very similar superblock, and suggests to clear the fake one;
>
On Sunday November 8, berbe...@fmi.uni-passau.de wrote:
> hello,
>
> Am Sonntag, den 08. November schrieb M G Berberich:
> > still not working with mdadm 3.0.3-2. During boot it failes with:
> >
> > Begin: Assemble all MD arrays ... Failure: failed to assemble all arrays
> >
> > and then can
87 matches
Mail list logo
