On Sun, Apr 03, 2016 at 05:04:10AM +0200, Tilman Blumenbach wrote:
> I'm wondering - does this mean that quotas are now unusable in jessie and we
> have to wait until a new Debian stable release (or use testing)? Is there
> maybe a workaround for this issue for those who want (or have) to stick
On Sun, 03 Apr 2016 05:04:10 +0200 Tilman Blumenbach
wrote:
> Hello,
>
> On Sun, 20 Mar 2016 13:47:59 +0100 Michael Meskes
wrote:
> > I doubt it will make it into 8, although somebody might create a
> > backport. You may have to wait for the next release I'm
Hello,
On Sun, 20 Mar 2016 13:47:59 +0100 Michael Meskes wrote:
> I doubt it will make it into 8, although somebody might create a
> backport. You may have to wait for the next release I'm afraid.
I'm wondering - does this mean that quotas are now unusable in jessie and we
> I installed from the unstable to test in stable debian 8, and it
> working
> fine!
Thanks, good to hear that.
> Will it be aviable for update in Debian 8 or just in the next, Debian
> 9
I doubt it will make it into 8, although somebody might create a
backport. You may have to wait for the
2016-03-20 12:23 időpontban Michael Meskes ezt írta:
> This Bug is still alive!
> ...
root@mark:/# dpkg -l | grep quota
ii quota 4.01-
8 amd64
disk quota management tools
No surprise, the bug was fixed in version 4.03-2!
Michael
O,
> > This Bug is still alive!
> > ...
> root@mark:/# dpkg -l | grep quota
> ii quota 4.01-
> 8 amd64
> disk quota management tools
No surprise, the bug was fixed in version 4.03-2!
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De,
2016-03-20 10:43 időpontban Gergo ezt írta:
This Bug is still alive!
If I Setup UsrQuota for the root partition, the systemd damages the
aquota.user file,
then the next restart, the quota doesn't start, then if I try start
manually, quota generates a totally new aquota.user file, so all
This Bug is still alive!
If I Setup UsrQuota for the root partition, the systemd damages the
aquota.user file,
then the next restart, the quota doesn't start, then if I try start
manually, quota generates a totally new aquota.user file, so all
adjusted limits will be lose!
root@mark:~#
From boot:
[ OK ] Reached target Remote File Systems.
Starting Trigger Flushing of Journal to Persistent Storage...
Starting LSB: Raise network interfaces
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[5.091509] quotaon.sh[212]: Checking quotas...done.
[
My guess is the reason is systemd's enabling quota before our service is
enabled. Can you please check in journalctl if that's the case? You should have
entries there that talk about enabling quotas before quota.service is run, if
at all.
This needs to be fixed asap, but the question is how as
Hello,
same problem here on debian jessie
systemctl status quotaon.service
● quotaon.service - Enable File System Quotas
Loaded: loaded (/lib/systemd/system/quotaon.service; static)
Active: failed (Result: exit-code) since mer. 2016-02-03 12:41:03
CET; 1 day 20h ago
Docs:
Confirmed, same problem our jessie servers. We are not alone according
to quick google search.
--
Kepi
signature.asc
Description: PGP signature
Hi
I have similar problems. Somehow the filesystem quota gets enabled
before the quota.service target is run.
journalctl gives:
Oct 05 17:47:37 fs-bm-1 systemd[1]: quota.service: main process exited,
code=exited, status=1/FAILURE
Oct 05 17:47:37 fs-bm-1 systemd[1]: Failed to start Check And
Package: quota
Severity: important
Dear Maintainer,
When I reboot machine, quota not start clearly:
Before adduser:
/dev/xvda1: clean, 47881/655360 files, 431344/2620928 blocks
[3.917625] systemd-fsck[202]: /dev/xvdb1: clean, 13/65408 files,
8535/261632 blocks
[4.302976]
14 matches
Mail list logo