linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Ingo Franzki <ifranzki@linux.ibm.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Ilia Zykov <mail@izyk.ru>, Gang He <GHe@suse.com>
Subject: Re: [linux-lvm] pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"
Date: Wed, 11 Sep 2019 12:10:30 +0200	[thread overview]
Message-ID: <c2aa1b3a-ee9b-5f80-b2a4-85c9409b85c9@linux.ibm.com> (raw)
In-Reply-To: <116a2ce6-452e-5c7b-3bb6-e53461125824@izyk.ru>

On 11.09.2019 12:03, Ilia Zykov wrote:
> Maybe this?
> 
> Please note that this problem can also happen in other cases, such as
> mixing disks with different block sizes (e.g. SCSI disks with 512 bytes
> and s390x-DASDs with 4096 block size).
> 
> https://www.redhat.com/archives/linux-lvm/2019-February/msg00018.html

And the fix for this is already available upstream (Thanks David!):
https://sourceware.org/git/?p=lvm2.git;a=commit;h=0404539edb25e4a9d3456bb3e6b402aa2767af6b
> 
> 
> On 11.09.2019 12:17, Gang He wrote:
>> Hello List,
>>
>> Our user encountered a meta-data corruption problem, when run pvresize command after upgrading to LVM2 v2.02.180 from v2.02.120.
>>
>> The details are as below,
>> we have following environment:
>> - Storage: HP XP7 (SAN) - LUN's are presented to ESX via RDM
>> - VMWare ESXi 6.5
>> - SLES 12 SP 4 Guest
>>
>> Resize happened this way (is our standard way since years) - however - this is our first resize after upgrading SLES 12 SP3 to SLES 12 SP4 - until this upgrade, we
>> never had a problem like this:
>> - split continous access on storage box, resize lun on XP7
>> - recreate ca on XP7
>> - scan on ESX
>> - rescan-scsi-bus.sh -s on SLES VM
>> - pvresize  ( at this step the error happened)
>>
>> huns1vdb01:~ # pvresize /dev/disk/by-id/scsi-360060e80072a660000302a6600003274
>>  Error writing device /dev/sdaf at 4096 length 512.
>>  Failed to write mda header to /dev/sdaf fd -1
>>  Failed to update old PV extension headers in VG vghundbhulv_ar.
>>  Error writing device /dev/disk/by-id/scsi-360060e80072a660000302a66000031ec at 4096 length 512.
>>  Failed to write mda header to /dev/disk/by-id/scsi-360060e80072a660000302a66000031ec fd -1
>>  Failed to update old PV extension headers in VG vghundbhulk_ar.
>>  VG info not found after rescan of vghundbhulv_r2
>>  VG info not found after rescan of vghundbhula_r1
>>  VG info not found after rescan of vghundbhuco_ar
>>  Error writing device /dev/disk/by-id/scsi-360060e80072a660000302a66000031e8 at 4096 length 512.
>>  Failed to write mda header to /dev/disk/by-id/scsi-360060e80072a660000302a66000031e8 fd -1
>>  Failed to update old PV extension headers in VG vghundbhula_ar.
>>  VG info not found after rescan of vghundbhuco_r2
>>  Error writing device /dev/disk/by-id/scsi-360060e80072a660000302a660000300b at 4096 length 512.
>>  Failed to write mda header to /dev/disk/by-id/scsi-360060e80072a660000302a660000300b fd -1
>>  Failed to update old PV extension headers in VG vghundbhunrm02_r2.
>>
>> Any idea for this bug?
>>
>> Thanks a lot.
>> Gang
>>
>>
>> _______________________________________________
>> linux-lvm mailing list
>> linux-lvm@redhat.com
>> https://www.redhat.com/mailman/listinfo/linux-lvm
>> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>>
> 
> 
> 
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
> 


-- 
Ingo Franzki
eMail: ifranzki@linux.ibm.com  
Tel: ++49 (0)7031-16-4648
Fax: ++49 (0)7031-16-3456
Linux on IBM Z Development, Schoenaicher Str. 220, 71032 Boeblingen, Germany

IBM Deutschland Research & Development GmbH / Vorsitzender des Aufsichtsrats: Matthias Hartmann
Geschäftsführung: Dirk Wittkopp
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
IBM DATA Privacy Statement: https://www.ibm.com/privacy/us/en/

  reply	other threads:[~2019-09-11 10:10 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  9:17 Gang He
2019-09-11 10:01 ` Ilia Zykov
2019-09-11 10:03 ` Ilia Zykov
2019-09-11 10:10   ` Ingo Franzki [this message]
2019-09-11 10:20     ` Gang He
2019-10-11  8:11 ` Heming Zhao
2019-10-11  9:22   ` Heming Zhao
2019-10-11 10:38     ` Zdenek Kabelac
2019-10-11 11:50       ` Heming Zhao
2019-10-11 15:14   ` David Teigland
2019-10-12  3:23     ` Gang He
2019-10-12  6:34     ` Heming Zhao
2019-10-12  7:11       ` Heming Zhao
2019-10-14  3:07         ` Heming Zhao
2019-10-14  3:13         ` Heming Zhao
2019-10-16  8:50           ` Heming Zhao

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=c2aa1b3a-ee9b-5f80-b2a4-85c9409b85c9@linux.ibm.com \
    --to=ifranzki@linux.ibm.com \
    --cc=GHe@suse.com \
    --cc=linux-lvm@redhat.com \
    --cc=mail@izyk.ru \
    --subject='Re: [linux-lvm] pvresize will cause a meta-data corruption with error message "Error writing device at 4096 length 512"' \
    /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

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