linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Elana Hashman <Elana.Hashman@twosigma.com>
To: Liu Bo <obuil.liubo@gmail.com>
Cc: "tytso@mit.edu" <tytso@mit.edu>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	Thomas Walker <Thomas.Walker@twosigma.com>
Subject: RE: Phantom full ext4 root filesystems on 4.1 through 4.14 kernels
Date: Thu, 24 Jan 2019 14:40:13 +0000	[thread overview]
Message-ID: <c8a7a059fb334920bdf020e0b7c050bd@exmbdft5.ad.twosigma.com> (raw)
In-Reply-To: <CANQeFDD78G0f8V2YYKq+wMpiVPzmZ8SJ_6xWtgyZ6FvAUKpe8w@mail.gmail.com>

From: Liu Bo <obuil.liubo@gmail.com> 

> I wonder if this ext4 enabled bigalloc (can be checked by dumpe2fs -h $disk).
> So bigalloc is known to cause leak space, and it's been just fixed recently.

Doesn't look that way:

$ uname -a
Linux <hostname> 4.14.67-ts1 #1 SMP Wed Aug 29 13:28:25 UTC 2018 x86_64 GNU/Linux
$ sudo du -hxs /
20G     /
$ df -h /
Filesystem                                              Size  Used Avail Use% Mounted on
/dev/disk/by-uuid/<some-uuid>   50G   46G  1.1G  98% /
$ sudo dumpe2fs -h /dev/disk/by-uuid/<some-uuid>
dumpe2fs 1.42.5 (29-Jul-2012)
Filesystem volume name:   ROOT
Last mounted on:          /
Filesystem UUID:          <some-uuid>
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              3276800
Block count:              13107200
Reserved block count:     655360
Free blocks:              9260751
Free inodes:              3078348
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      1020
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    16
Filesystem created:       Tue Jan 16 18:48:13 2018
Last mount time:          Mon Oct  1 20:43:59 2018
Last write time:          Mon Oct  1 20:43:58 2018
Mount count:              7
Maximum mount count:      -1
Last checked:             Tue Jan 16 18:48:13 2018
Check interval:           0 (<none>)
Lifetime writes:          7159 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
First orphan inode:       2231477
Default directory hash:   half_md4
Directory Hash Seed:      8a6f6d03-37e7-409c-b8c9-d738e0b0a94a
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Journal size:             128M
Journal length:           32768
Journal sequence:         0x02a09116
Journal start:            24688


--
Elana Hashman
ehashman@twosigma.com

      reply	other threads:[~2019-01-24 14:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 17:59 Phantom full ext4 root filesystems on 4.1 through 4.14 kernels Elana Hashman
2018-11-08 18:13 ` Reindl Harald
2018-11-08 18:20   ` Elana Hashman
2018-11-08 18:47 ` Darrick J. Wong
2018-12-05 16:26   ` Elana Hashman
2019-01-23 19:59     ` Thomas Walker
2019-06-26 15:17       ` Thomas Walker
2019-07-11  9:23         ` Jan Kara
2019-07-11 14:40           ` Geoffrey Thomas
2019-07-11 15:23             ` Jan Kara
2019-07-11 17:10             ` Theodore Ts'o
2019-07-12 19:19               ` Thomas Walker
2019-07-12 20:28                 ` Theodore Ts'o
2019-07-12 21:47                   ` Geoffrey Thomas
2019-07-25 21:22                     ` Geoffrey Thomas
2019-07-29 10:09                       ` Jan Kara
2019-07-29 11:18                         ` ext4 file system is constantly writing to the block device with no activity from the applications, is it a bug? Dmitrij Gusev
2019-07-29 12:55                           ` Theodore Y. Ts'o
2019-07-29 21:12                             ` Dmitrij Gusev
2019-01-24  1:54 ` Phantom full ext4 root filesystems on 4.1 through 4.14 kernels Liu Bo
2019-01-24 14:40   ` Elana Hashman [this message]

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=c8a7a059fb334920bdf020e0b7c050bd@exmbdft5.ad.twosigma.com \
    --to=elana.hashman@twosigma.com \
    --cc=Thomas.Walker@twosigma.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=obuil.liubo@gmail.com \
    --cc=tytso@mit.edu \
    /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).