From: Olaf Hering <olaf@aepfle.de>
To: linux-ext4@vger.kernel.org
Subject: ext4 errors with full filesystem
Date: Thu, 13 Aug 2015 10:23:07 +0200 [thread overview]
Message-ID: <20150813082307.GA32614@aepfle.de> (raw)
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.
Olaf
root@probook:/dist/iso/sles11 # wget -m -np 'http://cdn.novell.com/prot/La2AdJJ4-Ok~/SLED-11-SP4-DVD-i586-GM-DVD1.iso'
...
Cannot write to ‘cdn.novell.com/prot/La2AdJJ4-Ok~/SLED-11-SP4-DVD-i586-GM-DVD1.iso’ (No space left on device).
root@probook:/dist/iso/sles11 # Aug 13 10:13:35 probook.fritz.box kernel: EXT4-fs (sda5): Delayed block allocation failed for inode 15695873 at logical offset 1942120 with max blocks 221 with error 28
Aug 13 10:13:49 probook.fritz.box kernel: EXT4-fs (sda5): This should not happen!! Data will be lost
Aug 13 10:14:06 probook.fritz.box kernel: EXT4-fs (sda5): Total free blocks count 0
Aug 13 10:14:06 probook.fritz.box kernel: EXT4-fs (sda5): Free/Dirty block details
Aug 13 10:14:07 probook.fritz.box kernel: EXT4-fs (sda5): free_blocks=0
Aug 13 10:14:07 probook.fritz.box kernel: EXT4-fs (sda5): dirty_blocks=221
Aug 13 10:14:07 probook.fritz.box kernel: EXT4-fs (sda5): Block reservation details
Aug 13 10:14:08 probook.fritz.box kernel: EXT4-fs (sda5): i_reserved_data_blocks=221
Filesystem volume name: DBG1S82E_dist
Last mounted on: /dist
Filesystem UUID: 62c145ba-e2ba-4592-b355-7bba833fc396
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery sparse_super large_file
Filesystem flags: signed_directory_hash
Default mount options: user_xattr acl
Filesystem state: clean
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 33554432
Block count: 268433408
Reserved block count: 26843
Free blocks: 2038421
Free inodes: 32683679
First block: 0
Block size: 2048
Fragment size: 2048
Reserved GDT blocks: 512
Blocks per group: 16384
Fragments per group: 16384
Inodes per group: 2048
Inode blocks per group: 256
Filesystem created: Sun Nov 10 14:01:47 2013
Last mount time: Wed Aug 12 08:49:02 2015
Last write time: Wed Aug 12 08:49:02 2015
Mount count: 285
Maximum mount count: -1
Last checked: Tue Apr 22 09:12:00 2014
Check interval: 0 (<none>)
Lifetime writes: 4960 MB
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
Default directory hash: half_md4
Directory Hash Seed: 19e1770c-aa3c-4aba-8108-e9a5c8792e09
Journal backup: inode blocks
Journal features: journal_incompat_revoke
Journal size: 64M
Journal length: 32768
Journal sequence: 0x0006a56b
Journal start: 10216
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2015-08-13 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 8:23 Olaf Hering [this message]
2015-08-14 2:42 ` ext4 errors with full filesystem Theodore Ts'o
2015-08-14 9:48 ` Olaf Hering
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=20150813082307.GA32614@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-ext4@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).