On 5/31/22 1:49 PM, Mike Snitzer wrote:
> On Tue, May 31 2022 at 3:00P -0400,
> Jens Axboe wrote:
>
>> On 5/31/22 12:58 PM, Mike Snitzer wrote:
>>> On Sun, May 29 2022 at 8:46P -0400,
>>> Jens Axboe wrote:
>>>
On 5/28/22 6:17 PM, Matthew Wilcox wrote:
> Not quite sure whose bug this
On Tue, May 31 2022 at 3:00P -0400,
Jens Axboe wrote:
> On 5/31/22 12:58 PM, Mike Snitzer wrote:
> > On Sun, May 29 2022 at 8:46P -0400,
> > Jens Axboe wrote:
> >
> >> On 5/28/22 6:17 PM, Matthew Wilcox wrote:
> >>> Not quite sure whose bug this is. Current Linus head running xfstests
> >>>
On 5/31/22 12:58 PM, Mike Snitzer wrote:
> On Sun, May 29 2022 at 8:46P -0400,
> Jens Axboe wrote:
>
>> On 5/28/22 6:17 PM, Matthew Wilcox wrote:
>>> Not quite sure whose bug this is. Current Linus head running xfstests
>>> against ext4 (probably not ext4's fault?)
>>>
>>> 01818 generic/250
On Sun, May 29 2022 at 8:46P -0400,
Jens Axboe wrote:
> On 5/28/22 6:17 PM, Matthew Wilcox wrote:
> > Not quite sure whose bug this is. Current Linus head running xfstests
> > against ext4 (probably not ext4's fault?)
> >
> > 01818 generic/250 run fstests generic/250 at 2022-05-28 23:48:09
On Tue, May 31, 2022 at 10:43:01AM +0200, Martin Wilck wrote:
> Hi Steve,
>
> On Thu, 2022-05-26 at 20:10 +, Schremmer, Steven wrote:
> > > From: Martin Wilck
> > > Sent: Thursday, May 19, 2022 9:47 AM
> > > Hi Steve,
> > >
> > > On Thu, 2022-05-19 at 13:18 +, Schremmer, Steven wrote:
>
Hmmm. I think this patch should fix your issues.
If the journal has been aborted (which happens as part of the
shutdown, we will never write out the commit block --- so it should be
fine to skip the writeback of any dirty inodes in data=ordered mode.
BTW, if you know that the file system is
Late reply but maybe it is still useful :)
On Thu 14-04-22 17:19:49, Donald Buczek wrote:
> We have a cluster scheduler which provides each cluster job with a
> private scratch filesystem (TMPDIR). These are created when a job starts
> and removed when a job completes. The setup works by
