lkml.org 
[lkml]   [2006]   [Jan]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 000 of 5] md: Introduction
    On Mon, Jan 23, 2006 at 02:54:28PM +0100, you [Heinz Mauelshagen] wrote:
    > >
    > > It is very tedious to have to debug a production system for a few hours in
    > > order to get the rootfs mounted after each kernel update.
    > >
    > > The lvm error messages give almost no clue on the problem.
    > >
    > > Worse yet, problem reports on these issues are completely ignored on the lvm
    > > mailing list, even when a patch is attached.
    > >
    > > (See
    > > http://marc.theaimsgroup.com/?l=linux-lvm&m=113775502821403&w=2
    > > http://linux.msede.com/lvm_mlist/archive/2001/06/0205.html
    > > http://linux.msede.com/lvm_mlist/archive/2001/06/0271.html
    > > for reference.)
    >
    > Hrm, those are initscripts related, not lvm directly

    With the ancient LVM1 issue, my main problem was indeed that mkinitrd did
    not reserve enough space for the initrd. The LVM issue I posted to the LVM
    list was that LVM userland (vg_cfgbackup.c) did not check for errors while
    writing to the fs. The (ignored) patch added some error checking.

    But that's ancient, I think we can forget about that.

    The current issue (please see the first link) is about the need to add
    a "sleep 5" between
    lvm vgmknodes
    and
    mount -o defaults --ro -t ext3 /dev/root /sysroot
    .

    Otherwise, mounting fails. (Actually, I added "sleep 5" after every lvm
    command in the init script and did not narrow it down any more, since this
    was a production system, each boot took ages, and I had to get the system up
    as soon as possible.)

    To me it seemed some kind of problem with the lvm utilities, not with the
    initscripts. At least, the correct solution cannot be adding "sleep 5" here
    and there in the initscripts...

    > Alright.
    > Is the initscript issue fixed now or still open ?

    It is still open.

    Sadly, the only two systems this currently happens are production boxes and
    I cannot boot them at will for debugging. It is, however, 100% reproducible
    and I can try reasonable suggestions when I boot them the next time. Sorry
    about this.

    > Had you filed a bug against the distros initscripts ?

    No, since I wasn't sure the problem actually was in the initscript. Perhaps
    it does do something wrong, but the "sleep 5" workaround is pretty
    suspicious.

    Thanks for the reply.



    -- v --

    v@iki.fi
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-01-23 18:36    [W:4.138 / U:0.376 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site