From: Carlos Maiolino <cmaiolino@redhat.com>
To: Eryu Guan <eguan@redhat.com>
Cc: Brian Foster <bfoster@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH V2] xfstests: Test filesystem lockup on full overprovisioned dm-thin
Date: Mon, 17 Jul 2017 12:51:55 +0200 [thread overview]
Message-ID: <20170717084130.dparhukikbbykac5@eorzea.usersys.redhat.com> (raw)
In-Reply-To: <20170714034640.GJ2478@eguan.usersys.redhat.com>
On Fri, Jul 14, 2017 at 11:46:40AM +0800, Eryu Guan wrote:
> On Thu, Jul 13, 2017 at 11:42:59AM -0400, Brian Foster wrote:
> > On Thu, Jul 13, 2017 at 03:12:08PM +0200, Carlos Maiolino wrote:
> > > With thin devices, it's possible to have a virtual device larger than
> > > the physical device itself, and such situation can cause problems to
> > > filesystems, once the filesystem 'believe' to have more space than it
> > > actually has.
> > >
> > > This can lead the filesystem to several weird behaviors. The one tested
> > > here is filesystem lockup.
> > >
> > > In case of XFS, it locks up when trying to writeback AIL metadata back
> > > to the filesystem, but, once there is no physical space available, XFS
> > > locks up and do not gracefuly handle this case.
> > >
> > > Other filesystems usually are remounted as read-only, so they already
> > > have this situation covered.
> > >
> > > Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
>
Somehow these messages were marked as read on my MUA.
Thanks for the review folks.
Time to finish the kernel fix for this test
Cheers
--
Carlos
prev parent reply other threads:[~2017-07-17 10:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 13:12 [PATCH V2] xfstests: Test filesystem lockup on full overprovisioned dm-thin Carlos Maiolino
2017-07-13 15:42 ` Brian Foster
2017-07-14 3:46 ` Eryu Guan
2017-07-17 10:51 ` Carlos Maiolino [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=20170717084130.dparhukikbbykac5@eorzea.usersys.redhat.com \
--to=cmaiolino@redhat.com \
--cc=bfoster@redhat.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
/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