From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 2/3] xfs: remove bitfield based superblock updates
Date: Sat, 27 Sep 2014 09:01:06 +1000 [thread overview]
Message-ID: <20140926230106.GO4945@dastard> (raw)
In-Reply-To: <20140926094550.GB10692@infradead.org>
On Fri, Sep 26, 2014 at 02:45:50AM -0700, Christoph Hellwig wrote:
> This breaks generic/230 for me on an x86-64 VM:
>
> --- tests/generic/230.out 2013-11-11 10:38:59.000000000 +0000
> +++ /root/xfstests/results//generic/230.out.bad 2014-09-26 09:47:37.000000000 +0000
> @@ -23,11 +23,8 @@
> Write 900k...
> Rewrite 1001k...
> Write 1000k...
> -pwrite64: Disk quota exceeded
> Write 4096...
> -pwrite64: Disk quota exceeded
> Touch 3+4
> Touch 5+6
> touch: cannot touch 'SCRATCH_MNT/file6': Disk quota exceeded
> Touch 5
> -touch: cannot touch 'SCRATCH_MNT/file5': Disk quota exceeded
Curious, I haven't seen any change in quota behaviour on any test as
a result of these changes. What's the config of your VM and xfstests
run?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2014-09-26 23:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 12:20 [PATCH 0/3 v2] xfs: superblock logging rework Dave Chinner
2014-09-25 12:20 ` [PATCH 1/3] xfs: consider freeze levels in xfs_fs_writable() Dave Chinner
2014-09-25 16:17 ` Christoph Hellwig
2014-09-25 21:03 ` Dave Chinner
2014-09-26 9:44 ` Christoph Hellwig
2014-09-29 12:18 ` Brian Foster
2014-09-25 12:20 ` [PATCH 2/3] xfs: remove bitfield based superblock updates Dave Chinner
2014-09-26 9:45 ` Christoph Hellwig
2014-09-26 23:01 ` Dave Chinner [this message]
2014-09-26 10:00 ` Christoph Hellwig
2014-09-26 23:02 ` Dave Chinner
2014-09-25 12:20 ` [PATCH 3/3] xfs: consolidate superblock logging functions Dave Chinner
2014-09-29 13:20 ` Brian Foster
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=20140926230106.GO4945@dastard \
--to=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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.