linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Kirubakaran Kaliannan <kirubak@zadarastorage.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: statvfs() return large f_bavail on a 10TB drive
Date: Fri, 13 Apr 2018 08:43:13 -0700	[thread overview]
Message-ID: <20180413154313.GC32099@magnolia> (raw)
In-Reply-To: <c126c0a025db7e4011b4461c1ff26601@mail.gmail.com>

On Fri, Apr 13, 2018 at 12:10:19PM +0530, Kirubakaran Kaliannan wrote:
> Hi All,
> 
> I have couple of  xfs filesystem  on a 10TB STAT drive.
> 
> After 50% of filesystem is full, the df –kH is returning a large f_bavail.
> 
> 
> Filesystem                   Size  Used Avail Use% Mounted on
> /dev/dm-4                     10T  -12T   22T    - /mnt/a
> /dev/dm-3                     10T  -12T   22T    - /mnt/b
> 
> I tried statvfs() and got the same large f_bavail as well,
> 
>         total filesystem size = 9763506176 KB
>         total Available size = 21279656740 KB

21279656740KB = 0x100000000000 | (about 50% of the space) ?

Bitflip?

--D

>         total used size = -11516150564 KB
> 
> We are using Ubuntu 3.18.19 Linux kernel/xfs.
> 
> If I unmount and mount the filesysem back, the f_bavail values are back to
> normal.
> 
> Can you please point me, if this is something a known issue got fixed in
> XFS in the later version, or any lead may help.
> It is difficult at this point of time to upgrade the XFS for this specific
> issue.
> 
> Thanks,
> -kiru
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2018-04-13 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-13  6:40 statvfs() return large f_bavail on a 10TB drive Kirubakaran Kaliannan
2018-04-13 15:43 ` Darrick J. Wong [this message]
2018-04-23  4:26   ` Kirubakaran Kaliannan
2018-04-30 22:26     ` Darrick J. Wong

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=20180413154313.GC32099@magnolia \
    --to=darrick.wong@oracle.com \
    --cc=kirubak@zadarastorage.com \
    --cc=linux-xfs@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;
as well as URLs for NNTP newsgroup(s).