linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
* [linux-lvm] lseek errors after pvcreate on RAID5
@ 2006-05-07 14:29 Ognyan Kulev
  2006-05-10  4:57 ` Ognyan Kulev
  0 siblings, 1 reply; 2+ messages in thread
From: Ognyan Kulev @ 2006-05-07 14:29 UTC (permalink / raw)
  To: linux-lvm

[-- Attachment #1: Type: text/plain, Size: 2229 bytes --]

Hi,

I've made RAID5 on 4 disks in (unreleased) Debian GNU/Linux Etch, which
means linux-image-2.6.15-1-686 2.6.15-8, mdadm 1.12.0-1 and lvm2
2.01.04-5.  Here is the output of mdadm -D /dev/md1:

/dev/md1:
         Version : 00.90.03
   Creation Time : Fri May  5 17:26:32 2006
      Raid Level : raid5
      Array Size : 467394816 (445.74 GiB 478.61 GB)
     Device Size : 155798272 (148.58 GiB 159.54 GB)
    Raid Devices : 4
   Total Devices : 4
Preferred Minor : 1
     Persistence : Superblock is persistent

     Update Time : Fri May  5 20:45:07 2006
           State : clean
  Active Devices : 4
Working Devices : 4
  Failed Devices : 0
   Spare Devices : 0

          Layout : left-symmetric
      Chunk Size : 64K

            UUID : 1f3449d3:840d444b:2a767e13:7f2f67b3
          Events : 0.102

     Number   Major   Minor   RaidDevice State
        0       3        2        0      active sync   /dev/hda2
        1       3       66        1      active sync   /dev/hdb2
        2      22        2        2      active sync   /dev/hdc2
        3      22       66        3      active sync   /dev/hdd2

The problem is that after pvcreate /dev/md1, pvs command shows the
following:

   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
   PV         VG   Fmt  Attr PSize      PFree
   /dev/hdd2       lvm2 --   248064.43T 248064.43T
   /dev/md1        lvm2 --      445.74G    445.74G

Any idea what's happening?

Regards,
ogi


[-- Attachment #2: md1.txt --]
[-- Type: text/plain, Size: 896 bytes --]

/dev/md1:
        Version : 00.90.03
  Creation Time : Fri May  5 17:26:32 2006
     Raid Level : raid5
     Array Size : 467394816 (445.74 GiB 478.61 GB)
    Device Size : 155798272 (148.58 GiB 159.54 GB)
   Raid Devices : 4
  Total Devices : 4
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Fri May  5 20:45:07 2006
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 0
  Spare Devices : 0

         Layout : left-symmetric
     Chunk Size : 64K

           UUID : 1f3449d3:840d444b:2a767e13:7f2f67b3
         Events : 0.102

    Number   Major   Minor   RaidDevice State
       0       3        2        0      active sync   /dev/hda2
       1       3       66        1      active sync   /dev/hdb2
       2      22        2        2      active sync   /dev/hdc2
       3      22       66        3      active sync   /dev/hdd2


[-- Attachment #3: pvs.txt --]
[-- Type: text/plain, Size: 983 bytes --]

  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
  PV         VG   Fmt  Attr PSize      PFree     
  /dev/hdd2       lvm2 --   248064.43T 248064.43T
  /dev/md1        lvm2 --      445.74G    445.74G


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [linux-lvm] lseek errors after pvcreate on RAID5
  2006-05-07 14:29 [linux-lvm] lseek errors after pvcreate on RAID5 Ognyan Kulev
@ 2006-05-10  4:57 ` Ognyan Kulev
  0 siblings, 0 replies; 2+ messages in thread
From: Ognyan Kulev @ 2006-05-10  4:57 UTC (permalink / raw)
  To: LVM general discussion and development

Ognyan Kulev wrote:
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   /dev/hdd2: lseek 4611824548366092288 failed: Invalid argument
>   PV         VG   Fmt  Attr PSize      PFree     
>   /dev/hdd2       lvm2 --   248064.43T 248064.43T
>   /dev/md1        lvm2 --      445.74G    445.74G

It's fixed now.  It looks like I have used/initialized hdd2 before RAID5
is completely built and there was some metadata garbage left in hdd2
made after starting RAID5 sync but before finishing.

Regards,
ogi

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-05-10  4:57 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-07 14:29 [linux-lvm] lseek errors after pvcreate on RAID5 Ognyan Kulev
2006-05-10  4:57 ` Ognyan Kulev

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).