From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 4 Jun 2018 13:52:33 -0500 From: David Teigland Message-ID: <20180604185233.GA28542@redhat.com> References: <20180604153434.GB19875@redhat.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Subject: Re: [linux-lvm] "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA" Reply-To: LVM general discussion and development List-Id: LVM general discussion and development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , List-Id: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Jim Haddad Cc: linux-lvm@redhat.com On Mon, Jun 04, 2018 at 11:26:29AM -0700, Jim Haddad wrote: > Do you think I'm right, that there are no lasting effects from having > ran into problem? Meaning, if I run 2.02.176/178/2018-06-01-stable > I'm all set, and don't need to copy all the data off the disk and redo > it? It's probably ok. With one of the good versions above, run 'vgs -vvvv' and check that the offsets look good. Then run a pointless command to write the metadata with -vvvv and check that the vg writes are happening correctly. "vgchange -vvvv --addtag foo " will write a new version of the metadata and won't have any effect on LVs.