From: David Teigland <teigland@redhat.com>
To: Jim Haddad <jimhaddad46@gmail.com>
Cc: linux-lvm@redhat.com
Subject: Re: [linux-lvm] "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
Date: Mon, 4 Jun 2018 13:52:33 -0500 [thread overview]
Message-ID: <20180604185233.GA28542@redhat.com> (raw)
In-Reply-To: <CAANaKqf91hdLSHs5CyX_AFaoV0L2Jr6mVE+RRCJODRUF0bM+hQ@mail.gmail.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 <vgname>" will write a new
version of the metadata and won't have any effect on LVs.
next prev parent reply other threads:[~2018-06-04 18:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-03 20:13 [linux-lvm] "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA" Inbox
2018-06-03 20:18 ` Inbox
2018-06-03 22:21 ` Inbox
2018-06-03 23:57 ` Inbox
2018-06-04 0:19 ` Inbox
2018-06-04 0:46 ` Jim Haddad
2018-06-04 2:47 ` Jim Haddad
2018-06-04 15:34 ` David Teigland
2018-06-04 16:35 ` David Teigland
2018-06-04 18:26 ` Jim Haddad
2018-06-04 18:52 ` David Teigland [this message]
2018-06-04 6:54 ` Patrick Mitchell
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=20180604185233.GA28542@redhat.com \
--to=teigland@redhat.com \
--cc=jimhaddad46@gmail.com \
--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.