System with quota enabled hangs after upgrade to 11.10

Bug #930551 reported by Thomas Schweikle
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
quota (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Install Ubuntu 10.10, upgrade to 11.04, then 11.10. System hangs after rebooting into 11.10.
Last message seen on screen:
EXT4-fs (dm-1): recovery complete
EXT4-fs (dm-1): mounted filesystem with ordered data mode. Opts: errors-ro,usrquota,grpquota

No shell, no login, no ssh. The system will hang there forever.

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: quota 4.00~pre1-7ubuntu1
Uname: Linux 3.1.10 x86_64
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Sat Feb 11 08:14:22 2012
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: quota
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Thomas Schweikle (tps) wrote :
Revision history for this message
Thomas Schweikle (tps) wrote :

The system the bug report was generated IS NOT THE ONE THE BUG IS AFFECTING. This is because launchpad does not allow to create a bug report without using the provided tool: ubuntu-bug. But: THIS TOOL CAN ONLY BE RUN ON SYSTEMS UP AND RUNNING. The system the bug is affecting HANGS and does NOT ALLOW TO TYPE A COMMAND like ubuntu-bug to generate a complete bug report automatically.

Revision history for this message
Thomas Schweikle (tps) wrote :
Revision history for this message
Thomas Schweikle (tps) wrote :

Upgrading from 10.10 to 11.04 worked. The system came up and ran.
Upgrading from 11.04 to 11.10 worked. The system does not come up complete.

Adding "init=/bin/bash" to the kernel commandline gives a shell and shows all devices are mounted. trying to boot from this commandline by starting init, makes the system hang again at the very same point. The boot-log does not tell about anything usefull, since it is not written.

Removing quota from fstab doesn't matter. The system hangs at the very same point.
Removing dm-0-mount from fstab keeps the system hanging.
Removing dm-1-mount from fstab keeps the system hanging.
Removing dm-0 and dm-1 from fstab brings the system up to login.

As soon as dm-0 or dm-1 are entered again into fstab the same problem again.
There must be something horribly broken with lvm.

It is, indeed possible to remove dm-0 and dm-1 from fstab, boot, then mount both manually, but that isn't a real option for a normaly headless running server!

Revision history for this message
Thomas Schweikle (tps) wrote :

This bug might entirely unrelated to quota, but related to lvm solely. I've set up a second machine for testing, this time keeping lvm-volumes beyond 2T.

Changed in quota (Ubuntu):
importance: Undecided → High
Revision history for this message
Thomas Schweikle (tps) wrote :

It doesn't really hang, but recalculates the quota, waiting until this process is done, but doesn't inform the user about what is going on ... :-(

On a machine equipped with about 4TiB hd space, this process can take some time (hours). Depending on how many files are stored. After this process ran once, blocking start up, it will run much faster later on, if it was done successfully once (minutes).

Quota recalculation does get really slow if volumes above 2T are involved. If I keep them beyond 2T all is OK, but increasing the size makes things bad. I am not sure about if it is a quota problem, or a lvm problem. Maybe both, since I could not find same effects if quota isn't used and volumes are above 2T.

Revision history for this message
James Page (james-page) wrote :

Downgrading to medium - sounds like the process does complete but takes a really long time.

Changed in quota (Ubuntu):
importance: High → Medium
Revision history for this message
Thomas Schweikle (tps) wrote :

Seems fixed with newer versions than available in Ubuntu 11.10

Changed in quota (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.