[Bug 597176] [NEW] Kernel crashes in seconds in quota is on on ext4 and nfs4
Krzysztof LeszczyĆski
chris.lesz at gmail.com
Tue Jun 22 09:52:19 UTC 2010
Public bug reported:
We got server with a single nfs export mounted on /export/0 (ext4,usrquota,grpquota)
It crashes just after nfsd is started if quota is on. If the export is mounted without usrquota,grpquota it runs smoothly.
The filesystem is clean (fsck -f detected nothing) and the filesystem is filled 13% (107G/735G).
It crashed 2-3 times, then I switched off quota and mounted /export just before starting nfs. Now it's been working smoothly for few hours but I'm pretty sure it would crash immediately after starting quota.
Before the first crash it's been working for 2 days but then it crashed
seconds after staring nfsd.
Attaching the captured log.
# uname -a
Linux lsd 2.6.32-22-server #36-Ubuntu SMP Thu Jun 3 20:38:33 UTC 2010 x86_64 GNU/Linux
# cat /proc/version_signature
Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-22-virtual 2.6.32-22.36
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-server 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-server x86_64
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access /dev/snd/: No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
Date: Tue Jun 22 11:23:42 2010
InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427)
Lspci:
Lsusb: Error: command ['lsusb'] failed with exit code 1:
ProcCmdLine: root=LABEL=hostnameroot ro nomodeset
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.UTF-8
SourcePackage: linux
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug filesystem lucid needs-upstream-testing
--
Kernel crashes in seconds in quota is on on ext4 and nfs4
https://bugs.launchpad.net/bugs/597176
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.
More information about the kernel-bugs
mailing list