tags 639830 + moreinfo unreproducible
thanks
On 26.05.2012 13:03, Michael Tokarev wrote:
When creating initramfs, alternative MD device names (/dev/md/X) apparently
are not handled correctly by mdadm initramfs hook
Ok. After quite some digging I was able to - sort of, anyway -
reproduce
On Sat, 26 May 2012, Michael Tokarev wrote:
tags 639830 + moreinfo unreproducible
thanks
On 26.05.2012 13:03, Michael Tokarev wrote:
When creating initramfs, alternative MD device names (/dev/md/X)
apparently are not handled correctly by mdadm initramfs hook
Ok. After quite some
On Sat, 26 May 2012, Cristian Ionescu-Idbohrn wrote:
On Sat, 26 May 2012, Michael Tokarev wrote:
tags 639830 + moreinfo unreproducible
thanks
On 26.05.2012 13:03, Michael Tokarev wrote:
When creating initramfs, alternative MD device names (/dev/md/X)
apparently are not handled
[Back to the original bugreport, after removing all private data]
On 26.05.2012 16:06, Cristian Ionescu-Idbohrn wrote:
On Sat, 26 May 2012, Michael Tokarev wrote:
On 26.05.2012 15:37, Cristian Ionescu-Idbohrn wrote:
On Sat, 26 May 2012, Michael Tokarev wrote:
Do you still remember how did you
On 26.05.2012 18:11, Michael Tokarev wrote:
[]
when generating the image. The only possible case I can think
of is when you listed
INITRDSTART=/dev/md0
(the same as for root filesystem in fstab), but using /dev/md/0
in mdadm.conf -- in this case, mkinitramfs reports:
W: mdadm: I am
On Sat, 26 May 2012, Michael Tokarev wrote:
On 26.05.2012 16:06, Cristian Ionescu-Idbohrn wrote:
hi mdadm 3.2.5-1tool to administer Linux MD arrays
..because it is sid, and this is mdadm version I uploaded to
unstable/sid just a few HOURS ago, and you already have it
On Sat, 26 May 2012, Michael Tokarev wrote:
There's another possibility -- to try to detect such a disparity
(when one place uses one name and another place uses alternative
name) and fail if found.
This sound like a good idea: detect the disparity and recommend the proper
alternative?
But
On 26.05.2012 19:03, Cristian Ionescu-Idbohrn wrote:
[]
Note also that you still have the same inconsistency -- you list
/dev/md/0 in mdadm.conf, but use /dev/md0 as root filesystem. I
can't say it works by design, more by a chance, it is better to
use consistent naming there.
Alright. You
On Wed, 31 Aug 2011, martin f krafft wrote:
Can you add 'set -x' to the top of the hook, remake the initramfs,
and put it somewhere for me to download (or
ftp://ftp.madduck.net/incoming)?
Alright. I see I've drawn too early conclusions :(
Luckly, I've been able to reproduce. After doing the
Package: mdadm
Version: 3.1.4-1+8efb9d1
Severity: important
Dear Maintainer,
*** Please consider answering these questions, where appropiate ***
* What led up to the situation?
unbootable system
* What exactly did you do (or not do) that was effective (or
ineffective)?
modify
also sprach Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com
[2011.08.30.1922 +0200]:
My experience is that everything boils down to device names.
/dev/md0 and /dev/md/0 is the same device, AFAICT.
They should be handled as equaly. This trivial patch:
These are handled the same
On Tue, 30 Aug 2011, martin f krafft wrote:
also sprach Cristian Ionescu-Idbohrn cristian.ionescu-idbo...@axis.com
[2011.08.30.1922 +0200]:
My experience is that everything boils down to device names.
/dev/md0 and /dev/md/0 is the same device, AFAICT.
They should be handled as equaly.
Can you add 'set -x' to the top of the hook, remake the initramfs,
and put it somewhere for me to download (or
ftp://ftp.madduck.net/incoming)?
Thanks,
--
.''`. martin f. krafft madduck@d.o Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'`
13 matches
Mail list logo
