From: Zdenek Kabelac <zkabelac@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: amwang@redhat.com, Hugh Dickins <hughd@google.com>,
linux-kernel@vger.kernel.org, Joe Thornber <ejt@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>,
Lukas Czerner <lczerner@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [linux-lvm] Regression with FALLOC_FL_PUNCH_HOLE in 3.5-rc kernel
Date: Wed, 04 Jul 2012 13:51:19 +0200 [thread overview]
Message-ID: <4FF42E37.50009@redhat.com> (raw)
In-Reply-To: <20120702133308.GB785@redhat.com>
Dne 2.7.2012 15:33, Mike Snitzer napsal(a):
> Not sure why you're testing such old kernels without regard for fixes
> (likely just a hopeful bisect?).
>
> In any case, you definitely need this commit (was also marked for
> stable): 0c535e0 v3.3-rc7 dm io: fix discard support
>
>
After some more crashed filesystems here is the outcome with trial patch from
Mikulas included:
https://bugzilla.redhat.com/show_bug.cgi?id=837607
Zdenek
WARNING: multiple messages have this Message-ID (diff)
From: Zdenek Kabelac <zkabelac@redhat.com>
To: Mike Snitzer <snitzer@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
Mikulas Patocka <mpatocka@redhat.com>,
Joe Thornber <ejt@redhat.com>,
LVM general discussion and development <linux-lvm@redhat.com>,
amwang@redhat.com, Alasdair G Kergon <agk@redhat.com>,
linux-kernel@vger.kernel.org, Lukas Czerner <lczerner@redhat.com>
Subject: Re: Regression with FALLOC_FL_PUNCH_HOLE in 3.5-rc kernel
Date: Wed, 04 Jul 2012 13:51:19 +0200 [thread overview]
Message-ID: <4FF42E37.50009@redhat.com> (raw)
In-Reply-To: <20120702133308.GB785@redhat.com>
Dne 2.7.2012 15:33, Mike Snitzer napsal(a):
> Not sure why you're testing such old kernels without regard for fixes
> (likely just a hopeful bisect?).
>
> In any case, you definitely need this commit (was also marked for
> stable): 0c535e0 v3.3-rc7 dm io: fix discard support
>
>
After some more crashed filesystems here is the outcome with trial patch from
Mikulas included:
https://bugzilla.redhat.com/show_bug.cgi?id=837607
Zdenek
next prev parent reply other threads:[~2012-07-04 11:51 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 11:41 [linux-lvm] Regression with FALLOC_FL_PUNCH_HOLE in 3.5-rc kernel Zdenek Kabelac
2012-06-30 13:20 ` Zdenek Kabelac
2012-06-30 19:55 ` [linux-lvm] " Hugh Dickins
2012-06-30 19:55 ` Hugh Dickins
2012-06-30 20:51 ` [linux-lvm] " Zdenek Kabelac
2012-06-30 20:51 ` Zdenek Kabelac
2012-06-30 23:10 ` [linux-lvm] " Hugh Dickins
2012-06-30 23:10 ` Hugh Dickins
2012-07-01 12:57 ` [linux-lvm] " Zdenek Kabelac
2012-07-01 12:57 ` Zdenek Kabelac
2012-07-01 18:45 ` [linux-lvm] " Hugh Dickins
2012-07-01 18:45 ` Hugh Dickins
2012-07-01 20:10 ` [linux-lvm] " Zdenek Kabelac
2012-07-01 20:10 ` Zdenek Kabelac
2012-07-01 22:03 ` [linux-lvm] " Zdenek Kabelac
2012-07-01 22:03 ` Zdenek Kabelac
2012-07-02 9:00 ` [linux-lvm] " Lukáš Czerner
2012-07-02 9:00 ` Lukáš Czerner
2012-07-02 10:35 ` [linux-lvm] " Lukáš Czerner
2012-07-02 10:35 ` Lukáš Czerner
2012-07-02 13:41 ` [linux-lvm] " Mike Snitzer
2012-07-02 13:41 ` Mike Snitzer
2012-07-02 13:33 ` [linux-lvm] " Mike Snitzer
2012-07-02 13:33 ` Mike Snitzer
2012-07-04 11:51 ` Zdenek Kabelac [this message]
2012-07-04 11:51 ` Zdenek Kabelac
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=4FF42E37.50009@redhat.com \
--to=zkabelac@redhat.com \
--cc=agk@redhat.com \
--cc=amwang@redhat.com \
--cc=ejt@redhat.com \
--cc=hughd@google.com \
--cc=lczerner@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-lvm@redhat.com \
--cc=snitzer@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.