From: Olaf Hering <olaf@aepfle.de>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 errors with full filesystem
Date: Fri, 14 Aug 2015 11:48:31 +0200 [thread overview]
Message-ID: <20150814094831.GA15865@aepfle.de> (raw)
In-Reply-To: <20150814024227.GC26095@thunk.org>
On Thu, Aug 13, Theodore Ts'o wrote:
> On Thu, Aug 13, 2015 at 10:23:07AM +0200, Olaf Hering wrote:
> >
> > I just got the output below in syslog with a full filesystem.
> > Should I be worried about inconsistent filesystem now, or is that just an
> > overly verbose message about ENOSPC? This is a 4.1.5 kernel.
>
> You don't need to worry about an inconsistent file system, but it's an
> error that isn't supposed to to happen. The warning message indicates
I ran fsck -f anyway. There was no lost+found, I think that was removed long ago
because it conflicted with tabcompletion (ls /dist/lo<tab>). Since there was no
space left fsck was unable to create it, I think:
/lost+found not found. Create<y>? yes
ext2fs_new_block: Could not allocate block in ext2 filesystem while trying to create /lost+found directory
Otherwise no errors reported.
> I'm curious about your workload. How big is your file system, and how
> fragmented is your file system per e2freefrag? And how quickly was
> various programs writing to the file system at the time when you ran
> out of space, and what sort of files and what was the average size
> that was getting dumped into the file system? Oh, and how much memory
> did you have in your system?
Meanwhile I removed some smaller files to gain some space:
root@probook:~ # df /dist
/dev/sda5 528336856 528142072 141098 100% /dist
root@probook:~ # e2freefrag /dev/disk/by-label/DBG1S82E_dist
Device: /dev/disk/by-label/DBG1S82E_dist
Blocksize: 2048 bytes
Total blocks: 268433408
Free blocks: 0 (0.0%)
Min. free extent: 2 KB
Max. free extent: 26108 KB
Avg. free extent: 1692 KB
Num. free extent: 115
HISTOGRAM OF FREE EXTENT SIZES:
Extent Size Range : Free extents Free Blocks Percent
2K... 4K- : 13 13 inf%
4K... 8K- : 10 21 inf%
8K... 16K- : 17 102 inf%
16K... 32K- : 12 129 inf%
32K... 64K- : 12 254 inf%
64K... 128K- : 6 295 inf%
128K... 256K- : 6 560 inf%
256K... 512K- : 2 359 inf%
512K... 1024K- : 5 1902 inf%
1M... 2M- : 8 5701 inf%
2M... 4M- : 9 12859 inf%
4M... 8M- : 9 27150 inf%
8M... 16M- : 4 24156 inf%
16M... 32M- : 2 23891 inf%
There was just wget writing the iso to it, it was downloaded with about
10MB/sec. The system has 8GB RAM.
Olaf
next prev parent reply other threads:[~2015-08-14 9:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 8:23 ext4 errors with full filesystem Olaf Hering
2015-08-14 2:42 ` Theodore Ts'o
2015-08-14 9:48 ` Olaf Hering [this message]
2015-08-14 15:51 ` Theodore Ts'o
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=20150814094831.GA15865@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-ext4@vger.kernel.org \
--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 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.