Linux LVM users
 help / color / mirror / Atom feed
From: Enrico Ferro <enrico.ferro@infocamere.it>
To: linux-lvm@redhat.com
Subject: [linux-lvm] Meaning of LV -missing_<x>_<x> devices
Date: Wed, 15 Jun 2011 19:25:45 +0200	[thread overview]
Message-ID: <4DF8EB19.6030106@infocamere.it> (raw)

Hi all,

after the extention of a logical volume (mysqld1) a new "ghost" logical volume
appeared with a <missing> suffix:

brw-rw---- 1 root disk 253, 38 Feb 15 20:53 vgmysql-mysqld1
brw-rw---- 1 root disk 253, 44 Jun 1 10:21 vgmysql-mysqld1-missing_4_0

Before performing this LV we partitioned and added a new LUN to the existing
vgmysql volume group (again, no errors reported).

We did not discovered this strange device immediately (the lvextend
command did not reported errors), only after resizing the file system.
The ext2fs operation aborted and so we started with investigation.

Commands like vgdisplay reported errors like:

# vgdisplay -s
/dev/mapper/vgmysql-mysqld1-missing_4_0: read failed after 0 of 4096 at 0: 
Input/output error
"vg00" 132.59 GB [28.78 GB used / 103.81 GB free]
"vgmysql" 811.95 GB [793.00 GB used / 18.95 GB free]

So online resize of the FS failed, we unmounted the LV, extended with
(apparent) success the filesystems and lived happy for a few days. Only
while a deep corruption of the FS appeared. :-(

A reboot cleaned up the strange "missing" LV, it is no more present.

The point is: what is the meaning of -missing_* device? When are they
generated (and why there are no warnings reported?)

thank your for your suggestions,
best regards,
-- 
Enrico

             reply	other threads:[~2011-06-15 17:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-15 17:25 Enrico Ferro [this message]
2011-06-15 17:43 ` [linux-lvm] Meaning of LV -missing_<x>_<x> devices Stuart D. Gathman
  -- strict thread matches above, loose matches on Subject: below --
2011-06-16 13:03 Enrico Ferro

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=4DF8EB19.6030106@infocamere.it \
    --to=enrico.ferro@infocamere.it \
    --cc=linux-lvm@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox