From: "Stuart D. Gathman" <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Bad disk?
Date: Wed, 10 Nov 2010 12:41:48 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.1011101235510.1807@bmsred.bmsi.com> (raw)
In-Reply-To: <4CDAAE84.5060806@gmail.com>
On Wed, 10 Nov 2010, Mauricio Tavares wrote:
> Those dm-0 messages do not make me happy. dmesg and vgchange make me think the
> problem is on the new drive:
Those dm-0 messages are probably a logical error. For instance, a snapshot
that is full would give those errors. You need to tell us what dm-0 is
mapped to. Look in /dev/mapper for starters.
> [ 268.024593] scsi 0:0:0:0: Direct-Access ATA ST3500320NS SN04 PQ:
> 0 ANSI: 5
> [ 268.024900] sd 0:0:0:0: [sdc] 976773168 512-byte logical blocks: (500
> GB/465 GiB)
> [ 268.024918] sd 0:0:0:0: Attached scsi generic sg2 type 0
> [ 268.024996] sd 0:0:0:0: [sdc] Write Protect is off
> [ 268.025003] sd 0:0:0:0: [sdc] Mode Sense: 00 3a 00 00
> [ 268.025046] sd 0:0:0:0: [sdc] Write cache: enabled, read cache: enabled,
> doesn't support DPO or FUA
> [ 268.025377] sdc: sdc1
> [ 268.049853] sd 0:0:0:0: [sdc] Attached SCSI disk
This is normal for your new disk.
> [ 335.467482] quiet_error: 3 callbacks suppressed
> [ 335.467492] Buffer I/O error on device dm-0, logical block 104857584
> [ 335.467540] Buffer I/O error on device dm-0, logical block 104857584
> [ 335.467589] Buffer I/O error on device dm-0, logical block 104857598
> [ 335.467615] Buffer I/O error on device dm-0, logical block 104857598
> [ 335.467647] Buffer I/O error on device dm-0, logical block 0
> [ 335.467671] Buffer I/O error on device dm-0, logical block 0
> [ 335.467703] Buffer I/O error on device dm-0, logical block 1
> [ 335.467734] Buffer I/O error on device dm-0, logical block 104857599
> [ 335.467762] Buffer I/O error on device dm-0, logical block 104857599
> [ 335.467788] Buffer I/O error on device dm-0, logical block 104857599
Again, this is on dm-0, not sdc.
> raub@strangepork:~$ sudo sfdisk -l /dev/sdc
>
> Disk /dev/sdc: 60801 cylinders, 255 heads, 63 sectors/track
> Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
>
> Device Boot Start End #cyls #blocks Id System
> /dev/sdc1 0+ 60800 60801- 488384001 8e Linux LVM
> /dev/sdc2 0 - 0 0 0 Empty
> /dev/sdc3 0 - 0 0 0 Empty
> /dev/sdc4 0 - 0 0 0 Empty
This is normal, not sure what is has to do with filesystem desciptors.
Tell us exactly what you mean by "put a LVM on it". Did you run
pvcreate? vgcreate? lvcreate? You might find the output of "pvs"
enlightening. That will tell us what PVs you have created.
And list /dev/mapper so we know what dm-0 is, and include the output of "lvs".
--
Stuart D. Gathman <stuart@bmsi.com>
Business Management Systems Inc. Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
next prev parent reply other threads:[~2010-11-10 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 14:39 [linux-lvm] Bad disk? Mauricio Tavares
2010-11-10 15:11 ` Phillip Susi
2010-11-10 17:56 ` Mauricio Tavares
2010-11-10 18:58 ` Ray Morris
2010-11-10 20:29 ` Mauricio Tavares
2010-11-10 17:41 ` Stuart D. Gathman [this message]
2010-11-10 20:35 ` Mauricio Tavares
2010-11-11 16:46 ` Stuart D. Gathman
2010-11-11 18:39 ` Mauricio Tavares
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=Pine.LNX.4.64.1011101235510.1807@bmsred.bmsi.com \
--to=stuart@bmsi.com \
--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;
as well as URLs for NNTP newsgroup(s).