[linux-lvm] lseek errors after pvcreate on RAID5

[Ognyan Kulev]

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