All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bader <thomasb@trash.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Does LVM compile on Sparc64?
Date: Fri Dec 14 15:38:01 2001	[thread overview]
Message-ID: <20011214224027.A122@trash.net> (raw)
In-Reply-To: <20011214191520.GA19114@tykepenguin.com>

Hi

In alphanet.ml.linux.lvm, you wrote:
>  See http://lists.sistina.com/pipermail/linux-lvm/2001-December/009950.html
>  
>  for a patch that should work.

Oh nice.  I didn't found this patch yet (searched with
google).

I applied it and it compiled without error.  But now, my
machine does not boot anymore - it hangs directly after it
has detected my raid arrays:

-->-->-->--
md: updating md0 RAID superblock on device
sdb1 [events: 00000022](write) sdb1's sb offset: 3145664
md: serializing resync, md0 has overlapping physical units
with md2!
sda1 [events: 00000022](write) sda1's sb offset: 3145664
.
... autorun DONE.
--<--<--<--

After this, it won't continue booting up.  I booted a backup
copy of my kernel image.  I saw, that after the above step
("... autorun DONE.") the kernel tries to mount my root
partition read-only.

My / is on a RAID1 array (/dev/md0) with ext2.  Does the LVM
code touch anything of these two?

Any other hints?

Thanks & Cheers
Thomas
-- 
  .-.   Thomas Bader · thomasb@trash.net.remove · http://www.t-bader.ch/  .-.
  oo|                                                                     oo|
 /`'\     Einen Unix-Shellaccount gibt es unter http://www.trash.net/    /`'\
(\_;/)       PGP Key-ID: 0x3A4B7F5D (RSA)  0x7584F5D8 (DSA/EG)          (\_;/)

  reply	other threads:[~2001-12-14 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-14 11:54 [linux-lvm] Does LVM compile on Sparc64? Thomas Bader
2001-12-14 13:13 ` Patrick Caulfield
2001-12-14 15:38   ` Thomas Bader [this message]
2001-12-17  2:19     ` Patrick Caulfield

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011214224027.A122@trash.net \
    --to=thomasb@trash.net \
    --cc=linux-lvm@sistina.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.