Bug 36835 – Install fails with single-partition using quota during installation

Bug 36835 - Install fails with single-partition using quota during installation


Summary:	Install fails with single-partition using quota during installation

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Quota
Version:	UCS 4.0
Hardware:	All Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.0-x
Assigned To:	UCS maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:	36488
	Show dependency tree / graph

Reported:	2014-11-18 19:16 CET by Philipp Hahn
Modified:	2019-01-03 07:18 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Philipp Hahn

2014-11-18 19:16:47 CET

PT 4.0-0
Custom partition with only one primary partition using quota.
Installation of the package "quota" fails with

># dpkg --configure quota
>Setting up quota (4.00-4.25.201403150632) ...
>[ ok ] Chcking quotas...done.
>[....] Turning on quotas..quotaon: using //aquota.group on /dev/vda1 [/]: No such >process
>quotaon: Quota format not supported in kernel.
>quotaon: using //aquota.user on /dev/vda1 [/]: No such process
>quotaon: Quota format not supported in kernel.
>invoke-rc.d: iniscript quota, action "start" failed.
>dpkg: error processing quota (--configure):
> subprocess installed post-installation script returned error exit status 2
>Errors were encountered while processing:
> quota

Doing a "modprobe quota_v1" and "modprobe quota_v2" here manually solved the problem.
Installation failed nevertheless because of that.

Comment 1 Stefan Gohmann

2019-01-03 07:18:33 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.