All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ognyan Kulev <ogi@fmi.uni-sofia.bg>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] lseek errors after pvcreate on RAID5
Date: Wed, 10 May 2006 07:57:17 +0300	[thread overview]
Message-ID: <446172AD.1080401@fmi.uni-sofia.bg> (raw)
In-Reply-To: <445E0440.70007@fmi.uni-sofia.bg>

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

      reply	other threads:[~2006-05-10  4:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-07 14:29 [linux-lvm] lseek errors after pvcreate on RAID5 Ognyan Kulev
2006-05-10  4:57 ` Ognyan Kulev [this message]

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=446172AD.1080401@fmi.uni-sofia.bg \
    --to=ogi@fmi.uni-sofia.bg \
    --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 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.