From: Dave Chinner <david@fromorbit.com>
To: Gabriel VLASIU <gabriel@vlasiu.net>
Cc: xfs@oss.sgi.com
Subject: Re: xfs fs shutdown when no more space available
Date: Mon, 26 May 2014 09:37:46 +1000 [thread overview]
Message-ID: <20140525233746.GR8554@dastard> (raw)
In-Reply-To: <alpine.LRH.2.03.1405252005430.25037@mail.vlasiu.net>
On Sun, May 25, 2014 at 08:32:04PM +0300, Gabriel VLASIU wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> Hi!
>
> Usually, when the xfs partition has no more space nothing happend except I
> cannot write new data. This was true for a long time. But it's seems that
> in 3.14.4 something has changed (3.14.x?):
>
> # dd if=/dev/urandom of=noise.dat count=4194304
> cp noise.dat 11.dat
> cp noise.dat 22.dat
> ....
>
> At some point the partition become full and I get this in logs:
>
> May 25 19:48:25 imhotep kernel: [26271.780894] XFS (loop0): xlog_write: reservation summary:
> May 25 19:48:25 imhotep kernel: [26271.780894] trans type = FSYNC_TS (36)
> May 25 19:48:25 imhotep kernel: [26271.780894] unit res = 9640 bytes
> May 25 19:48:25 imhotep kernel: [26271.780894] current res = -4 bytes
> May 25 19:48:25 imhotep kernel: [26271.780894] total reg = 0 bytes (o/flow = 0 bytes)
> May 25 19:48:25 imhotep kernel: [26271.780894] ophdrs = 0 (ophdr space = 0 bytes)
> May 25 19:48:25 imhotep kernel: [26271.780894] ophdr + reg = 0 bytes
> May 25 19:48:25 imhotep kernel: [26271.780894] num regions = 0
fe4c224 xfs: inode log reservations are still too small
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-05-25 23:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 17:32 xfs fs shutdown when no more space available Gabriel VLASIU
2014-05-25 23:37 ` Dave Chinner [this message]
2014-05-26 5:52 ` Gabriel VLASIU
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=20140525233746.GR8554@dastard \
--to=david@fromorbit.com \
--cc=gabriel@vlasiu.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox