View Issue Details

IDProjectCategoryView StatusLast Update
0010059Talerdeployment and operationspublic2025-08-31 17:09
ReporterChristian Grothoff Assigned Toschanzen Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Platformi7OSDebian GNU/LinuxOS Versionsqueeze
Product Versiongit (master) 
Target Version1.0 stretch goalsFixed in Version1.0 stretch goals 
Summary0010059: quota service did not start properly on firefly on reboot
DescriptionI had to restart it manually. The reason was that /dev/mapper/home aka /home was not mounted/ready when the quota.service wanted to start, at it then failed with:

May 27 12:48:01 firefly systemd[1]: Starting quota.service - Initial Check File System Quotas...
May 27 12:48:01 firefly quota-initial-check.sh[1866231]: Checking quotas...
May 27 12:48:01 firefly quota-initial-check.sh[1866243]: quotacheck: Cannot guess format from filename on /dev/mapper/home. Please specify format on commandline.
May 27 12:48:01 firefly systemd[1]: quota.service: Main process exited, code=exited, status=1/FAILURE
Additional InformationSolution is probably to defer starting it more, until /home is properly mounted.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

schanzen

2025-06-03 05:41

administrator   ~0025090

This is a different problem I think. The quotacheck command requires a type option for the /dev/mapper/home device because it cannot deduce the type from the name.
The command to call is:

# quotacheck -F vfsv1 -cugmv /home

(the -F vfsv1 is what is missing).

Now, I do not know how to fix quota.service. I did not find the service file :/

schanzen

2025-06-03 05:46

administrator   ~0025091

I think this problem may have solved itself now.

schanzen

2025-06-03 06:04

administrator   ~0025092

Ah I just saw that you did not actually reboot recently. So this issue is very likely gone because I already manually ran quotacheck with the option and the file triggering this check is already gone. I documented the setup

Issue History

Date ModifiedUsernameFieldChange
2025-06-01 21:33Christian GrothoffNew Issue
2025-06-01 21:33Christian GrothoffStatusnew => assigned
2025-06-01 21:33Christian GrothoffAssigned To => schanzen
2025-06-03 05:41schanzenNote Added: 0025090
2025-06-03 05:46schanzenNote Added: 0025091
2025-06-03 06:04schanzenStatusassigned => informing
2025-06-03 06:04schanzenResolutionopen => fixed
2025-06-03 06:04schanzenNote Added: 0025092
2025-06-03 17:52Christian GrothoffTarget Version => 1.0 stretch goals
2025-06-03 17:52Christian GrothoffFixed in Version => 1.0 stretch goals
2025-08-31 17:09Christian GrothoffStatusinforming => closed