FS#35531 - [linux] 3.9.4 During e4defrag /var - kernel panic

Attached to Project: Arch Linux
Opened by ajes (ajes) - Wednesday, 29 May 2013, 08:14 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Sunday, 21 July 2013, 21:12 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Critical
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
When I run e4defrag on /var (which is on separate logical volume) in runlevel 1, kernel panic offucrs.

Additional info:
* package version(s)
e2fsprogs 1.42.7-1
lvm2 2.02.98-3
linux 3.9.4-1


* config and/or log files etc.


Steps to reproduce:
telinit 1
e4defrag /var
*kernel panic*
   1.jpg (414.7 KiB)
   2.jpg (499 KiB)
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Sunday, 21 July 2013, 21:12 GMT
Reason for closing:  None
Additional comments about closing:  I migrated from Arch Linux to Fedora on my netbook, so I can't check it anymore. Thanks.
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 02 June 2013, 18:22 GMT
  • Field changed: Summary (During e4defrag /var - kernel panic → [linux] During e4defrag /var - kernel panic)
  • Field changed: Status (Unconfirmed → Waiting on Response)
  • Field changed: Category (Packages: Core → Upstream Bugs)
  • Task assigned to Thomas Bächler (brain0), Tobias Powalowski (tpowa)
Please report to upstream. There is nothing to do here. Remember that in such report, should show details about your ext4, for example the output of tune2fs -l, if your ext4 is native, or converted from ext3, mount options...
Comment by ajes (ajes) - Monday, 03 June 2013, 06:15 GMT
$ sudo tune2fs -l /dev/dysk/var
tune2fs 1.42.7 (21-Jan-2013)
Filesystem volume name: var
Last mounted on: /var
Filesystem UUID: 2fa0f96e-3e5a-487b-90b8-64a240efa1a4
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 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: 65536
Block count: 1048576
Reserved block count: 0
Free blocks: 972960
Free inodes: 63050
First block: 1
Block size: 1024
Fragment size: 1024
Reserved GDT blocks: 256
Blocks per group: 8192
Fragments per group: 8192
Inodes per group: 512
Inode blocks per group: 128
Flex block group size: 16
Filesystem created: Wed Jan 9 13:27:52 2013
Last mount time: Mon Jun 3 07:23:55 2013
Last write time: Mon Jun 3 07:23:55 2013
Mount count: 6
Maximum mount count: 200
Last checked: Fri May 31 13:54:38 2013
Check interval: 0 (<none>)
Lifetime writes: 38 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
Default directory hash: half_md4
Directory Hash Seed: 782067a8-7c8c-450e-955a-414b1ae1cf2b
Journal backup: inode blocks
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 21 July 2013, 20:31 GMT
Please check if 3.9.11 fixes this issue for you. (linux-stable::commit 1d9595ffd53baf1e9313d14d6670eb32370617a9)

Otherwise please report to upstream.
Comment by ajes (ajes) - Sunday, 21 July 2013, 20:42 GMT
I migrated from Arch Linux to Fedora on my netbook, so I can't check it anymore. Thanks.

Loading...