From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 61631] kernel BUG at fs/ext4/super.c:818 umounting md raid6 volume
Date: Wed, 18 Sep 2013 22:27:02 +0000 [thread overview]
Message-ID: <bug-61631-13602-QH4wnakS4K@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-61631-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=61631
--- Comment #4 from Jim Faulkner <jfaulkne@ccs.neu.edu> ---
FYI, this bug only appears after some period of usage. After a reboot, I can
umount without error. After a reboot and an rsync of the gentoo portage tree
to the filesystem, I can still umount without error. It seems the filesystem
only fails to unmount after the filesystem has been in use for a while.
However, it is quite consistent in failing to umount after several days of
usage.
Some more details on this filesystem:
thud ~ # df -h | grep md1
/dev/md1 7.2T 6.7T 488G 94% /nfs
thud ~ # df -i | grep md1
/dev/md1 484597760 41868439 442729321 9% /nfs
thud ~ # tune2fs -l /dev/md1
tune2fs 1.42.7 (21-Jan-2013)
Filesystem volume name: <none>
Last mounted on: /nfs
Filesystem UUID: a9f907fb-4d04-4a28-8164-a2ac4d5a26f4
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: (none)
Filesystem state: clean
Errors behavior: Remount read-only
Filesystem OS type: Linux
Inode count: 484597760
Block count: 1938377664
Reserved block count: 0
Free blocks: 127846725
Free inodes: 442729321
First block: 0
Block size: 4096
Fragment size: 4096
Reserved GDT blocks: 561
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 8192
Inode blocks per group: 512
Flex block group size: 16
Filesystem created: Sat Oct 9 08:53:46 2010
Last mount time: Wed Sep 18 18:25:38 2013
Last write time: Wed Sep 18 18:25:38 2013
Mount count: 4
Maximum mount count: 23
Last checked: Wed Sep 11 04:36:58 2013
Check interval: 15552000 (6 months)
Next check after: Mon Mar 10 04:36:58 2014
Lifetime writes: 18 TB
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: 1584912d-08c0-46a6-a652-60800c55c4df
Journal backup: inode blocks
thud ~ #
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2013-09-18 22:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 22:05 [Bug 61631] New: kernel BUG at fs/ext4/super.c:818 umounting md raid6 volume bugzilla-daemon
2013-09-18 22:06 ` [Bug 61631] " bugzilla-daemon
2013-09-18 22:07 ` bugzilla-daemon
2013-09-18 22:10 ` bugzilla-daemon
2013-09-18 22:27 ` bugzilla-daemon [this message]
2013-09-19 18:58 ` Theodore Ts'o
2013-09-19 0:58 ` bugzilla-daemon
2013-09-19 19:20 ` bugzilla-daemon
2013-09-20 22:41 ` bugzilla-daemon
2013-09-21 2:08 ` bugzilla-daemon
2013-09-21 2:11 ` bugzilla-daemon
2013-10-12 0:14 ` bugzilla-daemon
2013-10-12 0:17 ` bugzilla-daemon
2013-10-12 0:17 ` bugzilla-daemon
2013-10-12 0:19 ` bugzilla-daemon
2013-10-12 0:21 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:58 ` bugzilla-daemon
2013-10-15 7:59 ` bugzilla-daemon
2013-10-15 8:04 ` bugzilla-daemon
2013-10-20 2:10 ` bugzilla-daemon
2013-10-20 22:32 ` bugzilla-daemon
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=bug-61631-13602-QH4wnakS4K@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--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 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.