All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heinz J. Mauelshagen" <Mauelshagen@sistina.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] I/O error: dev 08:11, sector 0
Date: Thu, 19 Jul 2001 11:13:51 +0200	[thread overview]
Message-ID: <20010719111351.A28183@sistina.com> (raw)
In-Reply-To: <20010718231729.A791@digit-safe.dyndns.org>; from allanwind@mediaone.net on Wed, Jul 18, 2001 at 11:17:29PM -0400

Allan,

08:11 (/dev/sda11) shows that I/O error, you use /dev/sdb, which is 08:16
for your VG -> no problem for LVM.

Because /dev/sda11 seems to be configured, LVM reads it on its search for
physical volumes.

If you are not using /dev/sda11 for anything you are fine for the moment.

If there's a file system on /dev/sda11 *and* just the first sector is not
accessable, you can still happily access the filesystem, because it doesn't use
that sector at all.
But you should check and probably replace your sda drive to avoid
trouble in the future.

On Wed, Jul 18, 2001 at 11:17:29PM -0400, Allan M. Wind wrote:
> Hi,
> 
> Installed linux 2.4.6 + lvm 0.9.1beta7 with the kernel piece build
> as a module (patched lvm and the kernel, got the user tools from
> the .deb package of the right version).
> 
> # pvcreate /dev/sdb
> # vgcreate -s16 vg1 /dev/scsi/host0/bus0/target9/lun0/disc
>   (apparently, devfsd confuses lvcreate)

vgcreate? Yes, you need to use the full devfs paths for now.

Regards,
Heinz    -- The LVM Guy --

> # lvcreate -L5g -nusr vg1
> # mkfs -m0 /dev/vg1/usr
> # lvcreate -L5g -nvar vg1
> # mkfs -m0 /dev/vg1/var
> # lvcreate -L24.03g -nhome vg1
> # mkfs -m0 /dev/vg1/home
> 
> Updated /etc/fstab and:
> 
> # mount -a
> 
> Migrate data over, rebooted the box which does a:
> 
> # vgchange -a n
> 
> grub failed on me as the staging files were on lvm lv's
> (that is probably a bug as one should be able to boot without
> /usr), so booted off floppy.
> 
> Found that I had overlooked the check in /etc/init.d/lvm which
> fails unless lvm was compiled in (yes, it was docmented but it
> should probably be a tad smarter ;-) ).
> 
> # modprobe lvm-mod
> 
> (I might have had to do a vgscan & vgchange -a y)
> 
> # mount -a
> 
> so here is where I was looking for help... I get an I/O error
> but things come up:
> 
> # vgck -v
> vgck -- locking logical volume manager
> vgck -- finding all volume group(s)
> vgck -- checking volume group name "vg1"
> vgck -- checking existence of volume group "vg1"
> vgck -- reading volume group data for "vg1" from lvmtab
> vgck -- checking volume group consistency  of "vg1" in lvmtab
> vgck -- VGDA of "vg1" in lvmtab is consistent
> vgck -- reading volume group data for "vg1" from physical volume(s)
>  I/O error: dev 08:11, sector 0
> vgck -- checking volume group consistency  of "vg1" on physical volume
> vgck -- VGDA of "vg1" on physical volume is consistent
> vgck -- unlocking logical volume manager
> 
> Is this a problem and how do I fix it?  This problem did not exist
> before I rebooted.
> 
> Thanks in advance,
> 
> 
> /Allan
> -- 
> Allan M. Wind			email: allanwind@mediaone.net
> P.O. Box 2022			finger: awind@digit-safe.dyndns.org (GPG/PGP)
> Woburn, MA 01888-0022
> USA

*** Software bugs are stupid.
    Nevertheless it needs not so stupid people to solve them ***

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Heinz Mauelshagen                                 Sistina Software Inc.
Senior Consultant/Developer                       Am Sonnenhang 11
                                                  56242 Marienrachdorf
                                                  Germany
Mauelshagen@Sistina.com                           +49 2626 141200
                                                       FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

  reply	other threads:[~2001-07-19  9:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-19  3:17 [linux-lvm] I/O error: dev 08:11, sector 0 Allan M. Wind
2001-07-19  9:13 ` Heinz J. Mauelshagen [this message]
2001-07-19 12:48   ` Patrick Caulfield
2001-07-19 14:03     ` Heinz J. Mauelshagen
2001-07-19 13:10   ` Allan M. Wind
2001-07-19 14:06     ` Heinz J. Mauelshagen
2001-07-19 14:52       ` Allan M. Wind
2001-07-21  1:13         ` Allan M. Wind
2001-07-21 17:44           ` Allan M. Wind
2001-07-23  8:02             ` Heinz J. Mauelshagen
2001-07-23 14:31               ` Allan M. Wind

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=20010719111351.A28183@sistina.com \
    --to=mauelshagen@sistina.com \
    --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.