From: Inbox <jimhaddad46@gmail.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] "write failed.. No space left", "Failed to write VG", and "Failed to write a MDA"
Date: Sun, 3 Jun 2018 13:18:06 -0700 [thread overview]
Message-ID: <CAANaKqfsh0d8RSDXWDy9eaOwSS4OJP=C0h9x23-GsGZ7+yZHMQ@mail.gmail.com> (raw)
In-Reply-To: <CAANaKqdnGfgxxHwQVA+L3uNDe5aMydssLius94wcp6LxA1-w+g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2559 bytes --]
Kernel 4.16.8, lvm 2.02.177.
On Sun, Jun 3, 2018 at 1:13 PM, Inbox <jimhaddad46@gmail.com> wrote:
> I'm aware I can't let my thin volume get full. I'm actually about to
> delete a lot of things.
>
>
>
> I don't understand why it gave the sdh3 then sdh3, sdg3, sdf3 no space
> left on device errors. sdf3 has 366G left in its thin pool, and I asked to
> create a virtual 200G within it.
>
> I don't understand why it failed to write VG, or an MDA of VG.
>
> I'm most concerned if anything's corrupted now, or if I can ignore this
> other than that I couldn't create a volume.
>
> disk1thin is on sdh3
> disk2thin is on sdg3
> disk3thin is on sdf3
> disk4thin is on sde3
>
> # lvs
> ...
> disk1thin lvm twi-aot--- <4.53t
> 84.13 76.33
> disk2thin lvm twi-aot--- <4.53t
> 85.98 78.09
> disk3thin lvm twi-aot--- <4.53t
> 92.10 83.47
> disk4thin lvm twi-aot--- 4.53t
> 80.99 36.91
> ...
> # lvcreate -V200G lvm/disk3thin -n test3
> WARNING: Sum of all thin volume sizes (21.22 TiB) exceeds the size of
> thin pools and the size of whole volume group (<18.17 TiB).
> WARNING: You have not turned on protection against thin pools running
> out of space.
> WARNING: Set activation/thin_pool_autoextend_threshold below 100 to
> trigger automatic extension of thin pools before they get full.
> /dev/sdh3: write failed after 24064 of 24576 at 4993488961536: No space
> left on device
> Failed to write VG lvm.
> Failed to write VG lvm.
> Manual intervention may be required to remove abandoned LV(s) before
> retrying.
> # lvremove lvm/test3
> /dev/sdh3: write failed after 24064 of 24576 at 4993488961536: No space
> left on device
> WARNING: Failed to write an MDA of VG lvm.
> /dev/sdg3: write failed after 24064 of 24576 at 4993488961536: No space
> left on device
> WARNING: Failed to write an MDA of VG lvm.
> /dev/sdf3: write failed after 24064 of 24576 at 4993488961536: No space
> left on device
> WARNING: Failed to write an MDA of VG lvm.
> Logical volume "test3" successfully removed
> # lvs --- shows test3 is gone
>
> # pvs
> PV VG Fmt Attr PSize PFree
> /dev/sde3 lvm lvm2 a-- 4.54t <10.70g
> /dev/sdf3 lvm lvm2 a-- 4.54t 0
> /dev/sdg3 lvm lvm2 a-- 4.54t 0
> /dev/sdh3 lvm lvm2 a-- 4.54t 0
> # vgs
> VG #PV #LV #SN Attr VSize VFree
> lvm 4 51 0 wz--n- <18.17t <10.70g
>
>
[-- Attachment #2: Type: text/html, Size: 3665 bytes --]
next prev parent reply other threads:[~2018-06-03 20:18 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 [this message]
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
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='CAANaKqfsh0d8RSDXWDy9eaOwSS4OJP=C0h9x23-GsGZ7+yZHMQ@mail.gmail.com' \
--to=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 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).