Failed to start enable file system quotas как исправить

After I have installed a new hard disk, the system shows me the following message during the boot process: "[FAILED] Failed to start Enable File System Quotas". The NAS still seems to work normally. It is an external hard disk from Intenso with 2GB. I…


    • #1

    After I have installed a new hard disk, the system shows me the following message during the boot process:

    «[FAILED] Failed to start Enable File System Quotas».

    The NAS still seems to work normally.

    It is an external hard disk from Intenso with 2GB. I have shared a folder and set up a Samba share. My NAS based on a raspberry pi 4 two additional hard disks are connected.

    What can I do? Do I have to do anything?

    Many greetings and thank you very much,

    Jens

    • Offizieller Beitrag
    • #2

    File system quotas are disabled by default, so unless you enabled them and are getting this.. it’l shouldn’t be an issue.. just telling you it did not start.

    This is an old, old post.. but it more or less explains this and why it was disabled by default

    RE: OMV hangs on boot

    • #3

    Okay, thanks a lot for the fast answer.

    I did not enabled it by my self. Is there an option to disable file system quotas? This message appeared only after I connected the third hard-drive. With on lytwo drives the message did not appear. Is there a reason for that behavior?

    • Offizieller Beitrag
    • #4

    Okay, thanks a lot for the fast answer.

    I did not enabled it by my self. Is there an option to disable file system quotas? This message appeared only after I connected the third hard-drive. With on lytwo drives the message did not appear. Is there a reason for that behavior?

    It’s disabled by default (years ago, it was not). All that message is telling you is that it failed to load due to quotas being disabled.

    • #5

    Ah, okay. Now I get it!

    Thanks a lot!

Строки из fstab:

UUID=xxxx / ext4 errors=remount-ro 0 1
UUID=xxxx /media/Users ext4 errors=remount-ro,acl,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0 0 2

Может быть эти ошибки появляются после того, как стартует quotaon? Потому что при рабочем сервисе quota при запуске quotacheck будут появляться эти же ошибки.
Вывод sudo service quota status:

● quota.service - Check And Enable File System Quotas
   Loaded: loaded (/lib/systemd/system/quota.service; enabled)
   Active: failed (Result: exit-code) since Пн 2015-07-06 08:25:11 UTC; 2h 29min ago
     Docs: man:quotaon(8)
  Process: 227 ExecStart=/usr/share/quota/quotaon.sh (code=exited, status=2)
Main PID: 227 (code=exited, status=2)

июл 06 08:25:11 TestRemStor quotaon.sh[227]: Checking quotas...done.
июл 06 08:25:11 TestRemStor quotaon.sh[227]: Turning on quotas...quotaon: using /media/Users/aquota.group on /dev/sdc1 [/media/Users]: Устройст...урс занято
июл 06 08:25:11 TestRemStor systemd[1]: quota.service: main process exited, code=exited, status=2/INVALIDARGUMENT
июл 06 08:25:11 TestRemStor systemd[1]: Failed to start Check And Enable File System Quotas.
июл 06 08:25:11 TestRemStor systemd[1]: Unit quota.service entered failed state.
июл 06 08:25:11 TestRemStor quotaon.sh[227]: quotaon: using /media/Users/aquota.user on /dev/sdc1 [/media/Users]: Устройство или ресурс занято
Hint: Some lines were ellipsized, use -l to show in full.


Вывод sudo service quotaon status:

● quotaon.service - Enable File System Quotas
   Loaded: loaded (/lib/systemd/system/quotaon.service; static)
   Active: active (exited) since Пн 2015-07-06 08:25:10 UTC; 2h 31min ago
     Docs: man:quotaon(8)
  Process: 243 ExecStart=/sbin/quotaon -aug (code=exited, status=0/SUCCESS)
Main PID: 243 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/quotaon.service

Если нет ни у кого никаких соображений, подскажите, хотя бы, как отключить quotaon.service, чтобы он при запуске системы не включался?
Пробовал запуска ‘sudo systemctl disable quotaon.service’ — не выходит. Сервис всё равно запускается.

Не знаю почему, но отключение запуска сервиса quota.service снимает проблему, т.е. нужно выполнить:


sudo systemctl disable quota.service

После этого пропадают ошибки при запуске системы, сервис quotaon.service запускается, и квоты работают.
Считаю проблему решенной.

  1. 02.05.2016, 02:05


    #1

    Армаэль вне форума


    Senior Member

    Аватар для Армаэль


    По умолчанию quota напилась за первомай

    Здравия.
    Пришел сегодня наконец-то к компу (наотмечался. С первомаем, товарищи!), посмотрел на сервер выводом service —status-all и обнаружил что quota сдохла. Выглядит это так:

    Код:

    root@main:~# service --status-all
    ...
    [ - ]  quota
    [ - ]  quotarpc
    ...

    Код:

    root@main:~# service quota status
    ● quota.service - Check And Enable File System Quotas
       Loaded: loaded (/lib/systemd/system/quota.service; enabled)
       Active: failed (Result: exit-code) since Mon 2016-04-25 14:00:49 MSK; 6 days ago
         Docs: man:quotaon(8)
     Main PID: 326 (code=exited, status=6)
    Apr 25 14:00:49 main quotaon.sh[326]: Checking quotas...quotacheck: Quota for groups is enabled on mountpoint / so quotacheck might damage the file.
    Apr 25 14:00:49 main quotaon.sh[326]: Please turn quotas off or use -f to force checking.
    Apr 25 14:00:49 main systemd[1]: quota.service: main process exited, code=exited, status=6/NOTCONFIGURED
    Apr 25 14:00:49 main systemd[1]: Failed to start Check And Enable File System Quotas.
    Apr 25 14:00:49 main systemd[1]: Unit quota.service entered failed state.

    Да ещё и в 14:00 сдохла, сразу после того как ушел… Долго не думав, запустил service quota start, добавил в мониторинг.
    Чекнул quotarpc

    Код:

    root@main:~# service quotarpc status
    ● quotarpc.service - RPC Remote Quota Server
       Loaded: loaded (/lib/systemd/system/quotarpc.service; enabled)
       Active: inactive (dead)
               start condition failed at Mon 2016-04-25 14:00:49 MSK; 6 days ago
         Docs: man:rpc.rquotad(8)

    Получается что упала тоже в 14:00, но запуск её нечего не дал, не стартует:

    Код:

    root@main:~# service quotarpc status
    ● quotarpc.service - RPC Remote Quota Server
       Loaded: loaded (/lib/systemd/system/quotarpc.service; enabled)
       Active: inactive (dead)
               start condition failed at Sun 2016-05-01 21:03:34 MSK; 1s ago
               ConditionFileIsExecutable=/sbin/rpcbind was not met
         Docs: man:rpc.rquotad(8)

    А не когда не видел, чтобы quotarpc работал. Оно должно стартовать, или это левый процесс, который не нужен, если включен в возможностях квота(quota)? Не нашел инфы что эт вообще такое.

    Dedicated server Fujitsu-Siemens TX150 S7 | Intel Xeon X3470 | 32GB RAM ECC REG | IBM SAS 15k 300Gbx4 | WD SATA 7.2k 1Tbx4 | Intel Pro 1Gb LAN x2 | Ubuntu Server 18.04 LTS | ISPmanager 5 Lite


  2. 02.05.2016, 04:47


    #2

    VA вне форума


    Senior Member

    Аватар для VA


    По умолчанию

    Цитата Сообщение от Армаэль
    Посмотреть сообщение

    Да ещё и в 14:00 сдохла, сразу после того как ушел…

    25 апреля.

    <msg name=»26920″>Исправление включения квот на Debian с файловой системой xfs</msg>

    В одной из последних версий вроде поправлено (changelog уже несколько дней побитый), возможно в этом причина.


  3. 02.05.2016, 06:30


    #3

    Армаэль вне форума


    Senior Member

    Аватар для Армаэль


    По умолчанию

    Хм. Пролопатил логи, не вижу нечего с 25 апреля по сейдень отчего отрубилась quota. Не затирайте топик плз, если повториться — напишу сюда.
    А про quotarpc подскажите, то натыкаюсь на конфиги её, а что за херь не знаю, она должна быть вместе с quota запущена или можно не обращать внимания что она не стартует?

    Dedicated server Fujitsu-Siemens TX150 S7 | Intel Xeon X3470 | 32GB RAM ECC REG | IBM SAS 15k 300Gbx4 | WD SATA 7.2k 1Tbx4 | Intel Pro 1Gb LAN x2 | Ubuntu Server 18.04 LTS | ISPmanager 5 Lite


Ошибка загрузочного модуля ядра во время загружается

Я использую человечность 15.10 на ноутбуке лощины. Это хорошо работает, но недавно я получал медленное время начальной загрузки (~1 минута). Таким образом, я озирался и когда я читал /var/log/boot.log файл, я вижу следующую ошибку:

[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.

С любым сервисом (кроме tftpd) работающий отлично. Вот полный вывод:

[  OK  ] Started Load/Save Screen Backlight Brightness of backlight:intel_backlight.
[  OK  ] Reached target Sound Card.
[  OK  ] Created slice system-systemdx2drfkill.slice.
         Starting Load/Save RF Kill Switch Status of rfkill0...
[  OK  ] Started Show Plymouth Boot Screen.
[  OK  ] Started Forward Password Requests to Plymouth Directory Watch.
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill0.
[  OK  ] Started Check And Enable File System Quotas.
         Starting Load/Save RF Kill Switch Status of rfkill1...
[  OK  ] Started Braille Device Support.
         Starting Load Kernel Modules...
[FAILED] Failed to start Load Kernel Modules.
See 'systemctl status systemd-modules-load.service' for details.
[  OK  ] Started Load/Save RF Kill Switch Status of rfkill1.
[  OK  ] Started LSB: QEMU KVM module loading script.
[  OK  ] Found device ST500LM012_HN-M500MBB 8.
         Starting File System Check on /dev/sda8...
[  OK  ] Started File System Check on /dev/sda8.
         Mounting /mnt/ubuntuspace...
[  OK  ] Found device ST500LM012_HN-M500MBB 7.
         Activating swap /dev/disk/by-uuid/431a5631-95f2-4d4f-8f81-42e5801b57aa...
[  OK  ] Activated swap /dev/disk/by-uuid/431a5631-95f2-4d4f-8f81-42e5801b57aa.
[  OK  ] Reached target Swap.
[  OK  ] Mounted /mnt/ubuntuspace.
[  OK  ] Reached target Local File Systems.
         Starting Create Volatile Files and Directories...
         Starting Set console keymap...
[  OK  ] Reached target Remote File Systems.
         Starting Wait for all "auto" /etc/network/interfaces to be up for network-online.target...
         Starting LSB: AppArmor initialization...
         Starting Clean up any mess left by 0dns-up...
         Starting Tell Plymouth To Write Out Runtime Data...
[  OK  ] Started Wait for all "auto" /etc/network/interfaces to be up for network-online.target.
[  OK  ] Started Clean up any mess left by 0dns-up.
         Starting Nameserver information manager...
[  OK  ] Started Nameserver information manager.
[  OK  ] Started Set console keymap.
[  OK  ] Started Create Volatile Files and Directories.
         Starting Update UTMP about System Boot/Shutdown...
         Starting Network Time Synchronization...
[  OK  ] Started Update UTMP about System Boot/Shutdown.
[  OK  ] Started Network Time Synchronization.
[  OK  ] Reached target System Time Synchronized.
[  OK  ] Started LSB: AppArmor initialization.
         Starting LSB: Raise network interfaces....
[  OK  ] Started LSB: Raise network interfaces..
[  OK  ] Started Tell Plymouth To Write Out Runtime Data.
[  OK  ] Reached target System Initialization.
[  OK  ] Listening on UUID daemon activation socket.
         Starting Restore Sound Card State...
[  OK  ] Listening on D-Bus System Message Bus Socket.
[  OK  ] Started CUPS Scheduler.
[  OK  ] Listening on PC/SC Smart Card Daemon Activation Socket.
[  OK  ] Listening on CUPS Scheduler.
[  OK  ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[  OK  ] Started Trigger resolvconf update for networkd DNS.
[  OK  ] Reached target Paths.
[  OK  ] Started Daily Cleanup of Temporary Directories.
[  OK  ] Reached target Timers.
[  OK  ] Listening on ACPID Listen Socket.
[  OK  ] Reached target Sockets.
[  OK  ] Reached target Basic System.
         Starting Restore /etc/resolv.conf if the system crashed before the ppp link was shut down....
         Starting System Logging Service...
         Starting Permit User Sessions...
[  OK  ] Started Self Monitoring and Reporting Technology (SMART) Daemon.
         Starting Avahi mDNS/DNS-SD Stack...
         Starting LSB: Set the CPU Frequency Scaling governor to "ondemand"...
         Starting Detect the available GPUs and deal with any system changes...
         Starting LSB: Record successful boot for GRUB...
[  OK  ] Started Cgroup management daemon.
[  OK  ] Started CUPS Scheduler.
         Starting VirtualBox Linux kernel module...
         Starting LSB: automatic crash report generation...
         Starting Network Manager...
[  OK  ] Started Deferred execution scheduler.
[  OK  ] Started crash report submission daemon.
         Starting Modem Manager...
         Starting LSB: Load kernel modules needed to enable cpufreq scaling...
         Starting LSB: Start/stop sysstat's sadc...
         Starting Enable support for additional executable binary formats...
         Starting Accounts Service...
         Starting LSB: Speech Dispatcher...
         Starting Bluetooth service...
[  OK  ] Started Regular background program processing daemon.
         Starting Initialize hardware monitoring sensors...
         Starting LSB: daemon to balance interrupts for SMP systems...
[  OK  ] Started D-Bus System Message Bus.
[  OK  ] Started Avahi mDNS/DNS-SD Stack.
[  OK  ] Started Bluetooth service.
[  OK  ] Started Network Manager.
[  OK  ] Reached target Network.
[  OK  ] Started OpenBSD Secure Shell server.
         Starting MySQL Community Server...
         Starting OpenVPN service...
[  OK  ] Reached target Bluetooth.
[  OK  ] Started Make remote CUPS printers available locally.
         Starting LSB: Start daemon at boot time...
         Starting Thermal Daemon Service...
         Starting dnsmasq - A lightweight DHCP and caching DNS server...
         Starting PostgreSQL Cluster 9.4-main...
         Starting Login Service...
         Starting Network Manager Wait Online...
         Starting LSB: Monitor for system resources and process activity...
[  OK  ] Started System Logging Service.
[  OK  ] Started Restore Sound Card State.
[  OK  ] Started Restore /etc/resolv.conf if the system crashed before the ppp link was shut down..
[  OK  ] Started Permit User Sessions.
[  OK  ] Started LSB: Set the CPU Frequency Scaling governor to "ondemand".
[  OK  ] Started LSB: Record successful boot for GRUB.
[  OK  ] Started VirtualBox Linux kernel module.
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Started LSB: Load kernel modules needed to enable cpufreq scaling.
[  OK  ] Started LSB: Start/stop sysstat's sadc.
[  OK  ] Started LSB: Speech Dispatcher.
[  OK  ] Started LSB: daemon to balance interrupts for SMP systems.
[  OK  ] Started OpenVPN service.
[  OK  ] Started Initialize hardware monitoring sensors.
         Starting Hostname Service...
         Starting Authenticate and Authorize Users to Run Privileged Tasks...
         Mounting Arbitrary Executable File Formats File System...
         Starting LSB: set CPUFreq kernel parameters...
         Starting vboxweb-service.service...
         Starting vboxballoonctrl-service.service...
         Starting vboxautostart-service.service...
[  OK  ] Mounted Arbitrary Executable File Formats File System.
[  OK  ] Started LSB: set CPUFreq kernel parameters.
[  OK  ] Started vboxweb-service.service.
[  OK  ] Started vboxballoonctrl-service.service.
[  OK  ] Started vboxautostart-service.service.
[  OK  ] Started Enable support for additional executable binary formats.
[  OK  ] Started Hostname Service.
[  OK  ] Started Login Service.
[  OK  ] Started LSB: Monitor for system resources and process activity.
[  OK  ] Started Thermal Daemon Service.
[  OK  ] Started Authenticate and Authorize Users to Run Privileged Tasks.
[  OK  ] Started Accounts Service.
[  OK  ] Started Modem Manager.
[  OK  ] Started LSB: Start daemon at boot time.
[  OK  ] Started ACPI event daemon.
         Starting WPA supplicant...
[  OK  ] Started dnsmasq - A lightweight DHCP and caching DNS server.
[  OK  ] Reached target Host and Network Name Lookups.
[  OK  ] Started WPA supplicant.
         Starting Network Manager Script Dispatcher Service...
[  OK  ] Started Network Manager Script Dispatcher Service.
[  OK  ] Started MySQL Community Server.
[  OK  ] Started PostgreSQL Cluster 9.4-main.
         Starting PostgreSQL RDBMS...
[  OK  ] Started PostgreSQL RDBMS.
[  OK  ] Started Network Manager Wait Online.
[  OK  ] Reached target Network is Online.
         Starting LSB: start Samba daemons for the AD DC...
         Starting LSB: disk temperature monitoring daemon...
         Starting LSB: HPA's tftp server...
         Starting /etc/rc.local Compatibility...
         Starting LSB: Tool to automatically collect and submit kernel crash signatures...
         Starting LSB: Apache2 web server...
         Starting ISC DHCP IPv4 server...
         Starting LSB: Postfix Mail Transport Agent...
         Starting LSB: backup and restore program...
         Starting LSB: Starts or stops the xinetd daemon....
         Starting LSB: start Samba NetBIOS nameserver (nmbd)...
[  OK  ] Started LSB: disk temperature monitoring daemon.
[  OK  ] Started /etc/rc.local Compatibility.
[  OK  ] Started ISC DHCP IPv4 server.
[  OK  ] Started LSB: backup and restore program.
[FAILED] Failed to start LSB: HPA's tftp server.
See 'systemctl status tftpd-hpa.service' for details.
[  OK  ] Started LSB: Tool to automatically collect and submit kernel crash signatures.
         Starting Wait for Plymouth Boot Screen to Quit...
[  OK  ] Started LSB: Starts or stops the xinetd daemon..
[  OK  ] Started Detect the available GPUs and deal with any system changes.
         Starting Light Display Manager...

Вот вывод systemctl status systemd-modules-load.service :

● systemd-modules-load.service - Load Kernel Modules
   Loaded: loaded (/lib/systemd/system/systemd-modules-load.service; static; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2016-07-06 06:05:56 IST; 1h 13min ago
     Docs: man:systemd-modules-load.service(8)
           man:modules-load.d(5)
  Process: 1019 ExecStart=/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
 Main PID: 1019 (code=exited, status=1/FAILURE)

Jul 06 06:05:56 hostname systemd[1]: Starting Load Kernel Modules...
Jul 06 06:05:56 hostname systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jul 06 06:05:56 hostname systemd[1]: Failed to start Load Kernel Modules.
Jul 06 06:05:56 hostname systemd[1]: systemd-modules-load.service: Unit entered failed state.
Jul 06 06:05:56 hostname systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.

какова точно ошибка, она влияет на мое время начальной загрузки и как она должна быть зафиксирована?

задан
6 July 2016 в 14:54

поделиться

1 ответ

Что является «Отказавшим для запуска Модулей Ядра Загрузки»?

Systemd читает файлы в каталоге /etc/modules-load.d чтобы модули загрузились с этим сервисом. Если модули, указанные в этих файлах, не присутствуют в /lib/modules каталогу для загружаемого ядра, ошибка ‘не удалось запуститься, модули ядра загрузки’ появляется. Вот содержание /etc/modules-load.d каталог от ls -lA

-rw-r--r-- 1 root root 119 Apr 20 17:01 cups-filters.conf
lrwxrwxrwx 1 root root  10 May 12 10:39 modules.conf -> ../modules

Получите детали от journalctl

В моем случае вот соответствующая часть journalctl:

May 27 06:36:50 zanna-X205TA systemd-modules-load[176]: Failed to find module 'lp'
May 27 06:36:50 zanna-X205TA systemd-modules-load[176]: Failed to find module 'ppdev'
May 27 06:36:50 zanna-X205TA systemd-modules-load[176]: Failed to find module 'parport_pc'

Если Вы делаете journalctl | grep modules Вы будете видеть которые неудавшийся для загрузки

В моем случае, /etc/modules (указанный символьной ссылкой), было пусто, но cups-filters.conf файл содержал ссылки на модули, которые бросали ошибки:

# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc

То, чтобы заставлять сообщение исчезнуть

Мой ноутбук даже не имеет никаких параллельных портов, неудивительно, таким образом, мне не нужны те модули. В любом случае они не могли быть загружены, поскольку они не были в /lib/modules/$(uname -r)

Я прокомментировал те три строки (помещение # в начале строки перед именем модуля для каждого), и сообщение об ошибке исчезло.

Я не заметил различия во время начальной загрузки все же.

TL; DR

  • проверить journalctl видеть, каким модулям не удается загрузиться
  • считайте файлы в /etc/modules-load.d искать ссылки на те модули
  • прокомментируйте строки, которые указывают, что те модули для совершения ошибки исчезают (но сделайте резервную копию прежде, чем отредактировать),
  • перезагрузка, чтобы видеть, имеет ли это какое-либо значение ко времени начальной загрузки

ответ дан Zanna
6 July 2016 в 14:54

поделиться

Другие вопросы по тегам:

Похожие вопросы:

version graph

Reported by: heximcz <spacek@best-net.cz>

Date: Tue, 16 Jun 2015 16:39:05 UTC

Severity: important

Fixed in version quota/4.03-2

Done: Michael Meskes <meskes@debian.org>

Bug is archived. No further changes may be made.

Toggle useless messages


Report forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Tue, 16 Jun 2015 16:39:09 GMT) (full text, mbox, link).


Acknowledgement sent
to heximcz <spacek@best-net.cz>:
New Bug report received and forwarded. Copy sent to Michael Meskes <meskes@debian.org>.
(Tue, 16 Jun 2015 16:39:09 GMT) (full text, mbox, link).


Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

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] quotaon.sh[257]: Checking quotas...quotacheck: Quota for groups is enabled on mountpoint /home so quotacheck might damage the file.
[    4.303934] quotaon.sh[257]: Please turn quotas off or use -f to force checking.
[    4.309912] quotaon.sh[257]: quotacheck: Quota for users is enabled on mountpoint /home so quotacheck might damage the file.
[    4.310738] quotaon.sh[257]: Please turn quotas off or use -f to force checking.
[FAILED] Failed to start Check And Enable File System Quotas.
See 'systemctl status quota.service' for details.

With exist system user (with quota - 250MB):
/dev/xvda1: clean, 47880/655360 files, 431365/2620928 blocks
[    3.892881] systemd-fsck[199]: /dev/xvdb1: clean, 17/65408 files, 8539/261632 blocks
[    4.203950] quotaon.sh[256]: Checking quotas...
[FAILED] Failed to start Check And Enable File System Quotas.
See 'systemctl status quota.service' for details.
[  OK  ] Started Enable File System Quotas.


With both examples quota not running after reboot:

root@whng01:~# systemctl status quota.service
● quota.service - Check And Enable File System Quotas
   Loaded: loaded (/lib/systemd/system/quota.service; enabled)
   Active: failed (Result: exit-code) since Tue 2015-06-16 18:01:58 CEST; 33s ago
     Docs: man:quotaon(8)
  Process: 256 ExecStart=/usr/share/quota/quotaon.sh (code=exited, status=1/FAILURE)
 Main PID: 256 (code=exited, status=1/FAILURE)

Jun 16 18:01:58 whng01 quotaon.sh[256]: Checking quotas...
Jun 16 18:01:58 whng01 systemd[1]: quota.service: main process exited, code=exited, status=1/FAILURE
Jun 16 18:01:58 whng01 systemd[1]: Failed to start Check And Enable File System Quotas.
Jun 16 18:01:58 whng01 systemd[1]: Unit quota.service entered failed state.

After /etc/init.d/quota restart:

root@whng01:~# /etc/init.d/quota restart
[....] Restarting quota (via systemctl): quota.serviceJob for quota.service failed. See 'systemctl status quota.service' and 'journalctl -xn' for details.
 failed!

root@whng01:~# /etc/init.d/quota restart
[....] Restarting quota (via systemctl): quota.serviceJob for quota.service failed. See 'systemctl status quota.service' and 'journalctl -xn' for details.
 failed!

root@whng01:~# /etc/init.d/quota restart
[....] Restarting quota (via systemctl): quota.serviceJob for quota.service failed. See 'systemctl status quota.service' and 'journalctl -xn' for details.
 failed!

root@whng01:~# systemctl status quota.service
● quota.service - Check And Enable File System Quotas
   Loaded: loaded (/lib/systemd/system/quota.service; enabled)
   Active: failed (Result: exit-code) since Tue 2015-06-16 18:23:17 CEST; 8s ago
     Docs: man:quotaon(8)
  Process: 1723 ExecStop=/usr/share/quota/quotaoff.sh (code=exited, status=0/SUCCESS)
  Process: 1816 ExecStart=/usr/share/quota/quotaon.sh (code=exited, status=1/FAILURE)
 Main PID: 1816 (code=exited, status=1/FAILURE)

Jun 16 18:23:17 whng01 quotaon.sh[1816]: Checking quotas...
Jun 16 18:23:17 whng01 systemd[1]: quota.service: main process exited, code=exited, status=1/FAILURE
Jun 16 18:23:17 whng01 systemd[1]: Failed to start Check And Enable File System Quotas.
Jun 16 18:23:17 whng01 systemd[1]: Unit quota.service entered failed state.


/etc/fstab setting:
UUID=xxxxxxxxx /home           ext4    errors=remount-ro,usrjquota=quota.user,grpjquota=quota.group,jqfmt=vfsv0 0 2

quota was been created with this commands:
quotacheck -avugm
quotaon -avug


root@whng01:~# dpkg --list quota
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                          Version                     Architecture                Description
+++-=============================================-===========================-===========================-================================================================================================
ii  quota                                         4.01-8                      amd64                       disk quota management tools


Best Regards,
HeximCZ


-- System Information:
Debian Release: 8.1
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/16 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)



Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Mon, 05 Oct 2015 16:09:04 GMT) (full text, mbox, link).


Acknowledgement sent
to Hendrik Naumann <hn75@gmx.de>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Mon, 05 Oct 2015 16:09:04 GMT) (full text, mbox, link).


Message #10 received at 788963@bugs.debian.org (full text, mbox, reply):

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 Enable
File System Quotas.
Oct 05 17:47:37 fs-bm-1 systemd[1]: Unit quota.service entered failed state.

To check this I introduced "quotaon -ap" into/usr/share/quota/quotaon.sh
 on line 48 (before "LC_MESSAGES=C $on -ap|grep -q "is off" || exit 0").

After introducing the line the journal reads like this

Oct 05 17:50:40 fs-bm-1 quotaon.sh[278]: group quota on /srv/nfs4/users
(/dev/mapper/fs--ng--1_vg1-home_lv) is off
Oct 05 17:50:40 fs-bm-1 quotaon.sh[278]: user quota on /srv/nfs4/users
(/dev/mapper/fs--ng--1_vg1-home_lv) is on
Oct 05 17:50:40 fs-bm-1 systemd[1]: quota.service: main process exited,
code=exited, status=1/FAILURE
Oct 05 17:50:40 fs-bm-1 systemd[1]: Failed to start Check And Enable
File System Quotas.
Oct 05 17:50:40 fs-bm-1 systemd[1]: Unit quota.service entered failed state.

Because group quota is off quotaon.sh continues but since the userquota
is already set on the final "quotaon -aug" fails.

quotaon -aug
quotaon: using /srv/nfs4/users/aquota.user on
/dev/mapper/fs--ng--1_vg1-home_lv [/srv/nfs4/users]: Device or resource busy

If the quotas needs to be checked this may fail for the same reasons.

I am not shure, but this may also lead to wrong quota informations after
file system crashes?

Thanks

Hendrik Naumann

PS. fstab reads:

UUID="bc0d7c7e-2b6b-4010-b5e5-36bc94c21443"     /srv/nfs4/users ext4
defaults,acl,quota      0       2
/srv/nfs4/users  /home/users   none    defaults,bind   0       0










Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Tue, 02 Feb 2016 23:15:08 GMT) (full text, mbox, link).


Acknowledgement sent
to Kepi <debian@orthank.net>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Tue, 02 Feb 2016 23:15:08 GMT) (full text, mbox, link).


Message #15 received at 788963@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]
Confirmed, same problem our jessie servers. We are not alone according
to quick google search.

-- 
Kepi
[signature.asc (application/pgp-signature, inline)]

Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Fri, 05 Feb 2016 08:51:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Pascal Legrand <pascal.legrand@univ-orleans.fr>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Fri, 05 Feb 2016 08:51:03 GMT) (full text, mbox, link).


Message #20 received at 788963@bugs.debian.org (full text, mbox, reply):

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: man:quotaon(8)
  Process: 1380 ExecStart=/sbin/quotaon -aug (code=exited, status=2)
 Main PID: 1380 (code=exited, status=2)

févr. 03 12:41:03 samba4 quotaon[1380]: quotaon: utilisation de 
/home/aquota.group sur /dev/sda9 [/home] : Périphérique ou ressource occupé
févr. 03 12:41:03 samba4 quotaon[1380]: quotaon: utilisation de 
/home/aquota.user sur /dev/sda9 [/home] : Périphérique ou ressource occupé
févr. 03 12:41:03 samba4 systemd[1]: quotaon.service: main process 
exited, code=exited, status=2/INVALIDARGUMENT
févr. 03 12:41:03 samba4 systemd[1]: Failed to start Enable File System 
Quotas.
févr. 03 12:41:03 samba4 systemd[1]: Unit quotaon.service entered failed 
state.





-- 
Pascal




Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#788963; Package quota.
(Sun, 28 Feb 2016 11:54:08 GMT) (full text, mbox, link).


Acknowledgement sent
to Michael Meskes <meskes@debian.org>:
Extra info received and forwarded to list.
(Sun, 28 Feb 2016 11:54:08 GMT) (full text, mbox, link).


Message #25 received at 788963@bugs.debian.org (full text, mbox, reply):

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 systemd offers
features, like automatic on demand checking when a device is connected, that
the quota package doesn't have, while systemd lacks other features, like
quota's creation of quota files and check only when not clean unmounted. This
information is pre-Jessie so it might have changed but you get the gist.

Michael

-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Fri, 04 Mar 2016 20:48:06 GMT) (full text, mbox, link).


Acknowledgement sent
to Kepi <debian@orthank.net>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Fri, 04 Mar 2016 20:48:06 GMT) (full text, mbox, link).


Message #30 received at 788963@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]
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.
[    5.136692] systemd-journald[207]: Received request to flush runtime journal from PID 1
[    5.139098] quotaon.sh[212]: Turning on quotas...quotaon: using //aquota.group on /dev/xvda [/]: Device or resource busy
[    5.140942] quotaon.sh[212]: quotaon: using //aquota.user on /dev/xvda [/]: Device or resource busy
[FAILED] Failed to start Check And Enable File System Quotas.
See 'systemctl status quota.service' for details.

relevant part from syslog:

Feb 29 23:38:12 antonio quotaon.sh[212]: Checking quotas...done.
Feb 29 23:38:12 antonio quotaon.sh[212]: Turning on quotas...quotaon: using //aquota.group on /dev/xvda [/]: Device or resource busy
Feb 29 23:38:12 antonio quotaon.sh[212]: quotaon: using //aquota.user on /dev/xvda [/]: Device or resource busy
Feb 29 23:38:12 antonio systemd[1]: quota.service: main process exited, code=exited, status=2/INVALIDARGUMENT
Feb 29 23:38:12 antonio systemd[1]: Unit quota.service entered failed state.
Feb 29 23:38:12 antonio kernel: [    0.710525] VFS: Disk quotas dquot_6.5.2
Feb 29 23:38:12 antonio kernel: [    4.498800] EXT4-fs (xvda): re-mounted. Opts: errors=remount-ro,usrquota,grpquota

Its all information I currently have. If you need more information for
fixing this bug, let me know. I'll try to recreate this environment
again. I'm not able to restart that server again.

Thanks

-- 
Kepi

Michael Meskes <meskes@debian.org> writes:

> 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 systemd offers
> features, like automatic on demand checking when a device is connected, that
> the quota package doesn't have, while systemd lacks other features, like
> quota's creation of quota files and check only when not clean unmounted. This
> information is pre-Jessie so it might have changed but you get the gist.
>
> Michael
[signature.asc (application/pgp-signature, inline)]

Reply sent
to Michael Meskes <meskes@debian.org>:
You have taken responsibility.
(Sun, 06 Mar 2016 17:30:14 GMT) (full text, mbox, link).


Notification sent
to heximcz <spacek@best-net.cz>:
Bug acknowledged by developer.
(Sun, 06 Mar 2016 17:30:14 GMT) (full text, mbox, link).


Message #35 received at 788963-close@bugs.debian.org (full text, mbox, reply):

Source: quota
Source-Version: 4.03-2

We believe that the bug you reported is fixed in the latest version of
quota, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 788963@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Michael Meskes <meskes@debian.org> (supplier of updated quota package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sun, 06 Mar 2016 15:57:40 +0100
Source: quota
Binary: quota
Architecture: source amd64
Version: 4.03-2
Distribution: unstable
Urgency: medium
Maintainer: Michael Meskes <meskes@debian.org>
Changed-By: Michael Meskes <meskes@debian.org>
Description:
 quota      - disk quota management tools
Closes: 753939 780977 788963
Changes:
 quota (4.03-2) unstable; urgency=medium
 .
   * With systemd only test after installation, the rest is handled by systemd.
     (Closes: #753939, #780977, #788963)
   * Bumped Standards-Version to 3.9.7, no changes needed.
Checksums-Sha1:
 29caf15d83217eb551042d41b3c6f162f8143777 1864 quota_4.03-2.dsc
 95d76ba29d316b8626e47bb17285f5d170d0858d 39264 quota_4.03-2.debian.tar.xz
 3fcba15505e0f0048cc57093bff99be0713702c3 1120084 quota-dbgsym_4.03-2_amd64.deb
 82d9936fb3468ba8633eece4e72b7e34b33a36e3 315530 quota_4.03-2_amd64.deb
Checksums-Sha256:
 503b8200c549d7fbab78a787171d79eec058fffa8abdb6cb83e7d10838db414e 1864 quota_4.03-2.dsc
 f1a9a8228a3eb031c79f398e8526f09e1625182d63460238b32d208e9eb00817 39264 quota_4.03-2.debian.tar.xz
 130b41f31ca0220da171513077800f4da52e4fe59ed893044a2aba189996ecf6 1120084 quota-dbgsym_4.03-2_amd64.deb
 38c84e16761d3064c3c1d6a83b70e2beffc97fe3e7b155d7342151550990f725 315530 quota_4.03-2_amd64.deb
Files:
 87b904f61fcd7ca88b68f5eccb88ce9a 1864 admin optional quota_4.03-2.dsc
 c2713de642576a30a7f16b316a83f28b 39264 admin optional quota_4.03-2.debian.tar.xz
 a9e2bdbe9e780460e6e3dff1c88998d8 1120084 debug extra quota-dbgsym_4.03-2_amd64.deb
 a6e313d6998cee9a6d6fc09651917e22 315530 admin optional quota_4.03-2_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIVAwUBVtxlBN8j2jOWl46zAQiD+RAArhaQ1Ps5/iyECXnxJlL/ZWrmCvH3P8ru
kFnGBHl7BzP2yqNiicS6Hc5LBtwXBIdXxTrG316JnxyAz/prZWcroNDUtApEusxf
6c2aCKfs4hh/nq1Px6Kxnjd64T/6OKIBsWs8VaYPULzHi8CzTeWScY8gO3gzWi8U
6NlfV+x+tRY4VOSN32IcUAY1Zk+llIGzmaprCAMEl9Vuu4ed1+oinC4olzGrPwgb
RXgQQ04uKYYqiogjCKOSTaqm/DyDyIJmUJAkVALNqC/A+k8MAxQMEBovryQ5ifp7
hFT7zHKRJdNwmWFDRnKjdSkI20pMcBmh8KRT9a0Q86W3t/LBu1jkRO/n8fy22Scn
VdTe/ohk+UY6HIQ0KA1YXreJqokLobEkCGUg7LUficweuuEBhuEDLRwt7XraruQM
vKWAo8MlYpM0Ceg/p0tJ6utk5tV1uJtYvoSTrEivEzyym5BQlTmyW7kDMUlRBvWX
ql9tv419qUySdwQ5AJC/drZN8Tfzr5Dds/d+M4vocpzQ3YVbQFqmlDHpkjCHrmZn
W+TAkgrQoPZbjjjiVcTKnoDIRV/fgWrVAtMrScqt7xdFp0HQapjIztBZBeTNvJrD
ZcpAjdSaNzHrBSlp9BhByzfnDvhhX5cB8LYoI7bCtwOpKZvoIfWDAyYrTJo8tDSu
INrq2l3cABo=
=hG3e
-----END PGP SIGNATURE-----




Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Sun, 20 Mar 2016 09:57:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Gergo <gergo@bmrg.hu>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Sun, 20 Mar 2016 09:57:03 GMT) (full text, mbox, link).


Message #40 received at 788963@bugs.debian.org (full text, mbox, reply):

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:~# systemctl status quota.service
● quota.service - Check And Enable File System Quotas
   Loaded: loaded (/lib/systemd/system/quota.service; enabled)
   Active: failed (Result: exit-code) since v 2016-03-20 10:21:38 CET; 
1min 18s ago
     Docs: man:quotaon(8)
  Process: 281 ExecStart=/usr/share/quota/quotaon.sh (code=exited, 
status=2)
 Main PID: 281 (code=exited, status=2)

márc 20 10:21:38 mark quotaon.sh[281]: Checking quotas...done.
márc 20 10:21:38 mark quotaon.sh[281]: Turning on quotas...quotaon: 
using //aquota.user on /dev/sda1 [/]: Az eszköz vagy erőforrás foglalt
márc 20 10:21:38 mark quotaon.sh[281]: quotaon: using /home/aquota.user 
on /dev/sda3 [/home]: Az eszköz vagy erőforrás foglalt
márc 20 10:21:38 mark systemd[1]: quota.service: main process exited, 
code=exited, status=2/INVALIDARGUMENT
márc 20 10:21:38 mark systemd[1]: Failed to start Check And Enable File 
System Quotas.
márc 20 10:21:38 mark systemd[1]: Unit quota.service entered failed 
state.


root@mark:~# cat /etc/fstab

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=5b3f238f-f23e-4145-b13d-cb80ca7aae9b /               ext4    
errors=remount-ro,usrquota   	0       1
# /home was on /dev/sda3 during installation
UUID=f4aa4f06-5dc7-414e-a366-cc88c07b3596 /home           ext4	  
defaults,usrquota       	0       2
# swap was on /dev/sda5 during installation
UUID=1e962db3-aeef-40b3-9e1f-c3e1df761016 none            swap    sw     
         0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0



Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Sun, 20 Mar 2016 10:15:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Gergo <gergo@bmrg.hu>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Sun, 20 Mar 2016 10:15:04 GMT) (full text, mbox, link).


Message #45 received at 788963@bugs.debian.org (full text, mbox, reply):

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
> adjusted limits will be lose!
> 

Version: Debian 8.3

root@mark:/# dpkg -l | grep quota
ii  quota                          4.01-8                      amd64     
   disk quota management tools
ii  quotatool                      1:1.4.12-2                  amd64     
   tool to edit disk quotas from the command line
root@mark:/# uname -a
Linux mark 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 
(2016-02-29) x86_64 GNU/Linux
root@mark:/# cat /etc/debian_version
8.3



Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#788963; Package quota.
(Sun, 20 Mar 2016 11:27:04 GMT) (full text, mbox, link).


Acknowledgement sent
to Michael Meskes <meskes@debian.org>:
Extra info received and forwarded to list.
(Sun, 20 Mar 2016 11:27:04 GMT) (full text, mbox, link).


Message #50 received at 788963@bugs.debian.org (full text, mbox, reply):

> > 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, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL





Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Sun, 20 Mar 2016 11:57:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Gergo <gergo@bmrg.hu>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Sun, 20 Mar 2016 11:57:03 GMT) (full text, mbox, link).


Message #55 received at 788963@bugs.debian.org (full text, mbox, reply):

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, Thank you wery much!
I forgot to check 4.03-2 version.

I installed from the unstable to test in stable debian 8, and it working 
fine!
Will it be aviable for update in Debian 8 or just in the next, Debian 9 
?



Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#788963; Package quota.
(Sun, 20 Mar 2016 12:51:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Michael Meskes <meskes@debian.org>:
Extra info received and forwarded to list.
(Sun, 20 Mar 2016 12:51:03 GMT) (full text, mbox, link).


Message #60 received at 788963@bugs.debian.org (full text, mbox, reply):

> 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 next release I'm afraid.

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL





Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Sun, 03 Apr 2016 03:09:03 GMT) (full text, mbox, link).


Acknowledgement sent
to Tilman Blumenbach <tilman@ax86.net>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Sun, 03 Apr 2016 03:09:04 GMT) (full text, mbox, link).


Message #65 received at 788963@bugs.debian.org (full text, mbox, reply):

Hello, 

On Sun, 20 Mar 2016 13:47:59 +0100 Michael Meskes <meskes@debian.org> 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 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 to jessie? 

Regards, 

Tilman 


> 
> Michael
> -- 
> Michael Meskes
> Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
> Meskes at (Debian|Postgresql) dot Org
> Jabber: michael at xmpp dot meskes dot org
> VfL Borussia! Força Barça! SF 49ers! Use Debian GNU/Linux, PostgreSQL
> 
> 
> 
> 




Information forwarded
to debian-bugs-dist@lists.debian.org, Michael Meskes <meskes@debian.org>:
Bug#788963; Package quota.
(Mon, 04 Apr 2016 18:21:04 GMT) (full text, mbox, link).


Acknowledgement sent
to pathos flux <pathosflux@gmail.com>:
Extra info received and forwarded to list. Copy sent to Michael Meskes <meskes@debian.org>.
(Mon, 04 Apr 2016 18:21:05 GMT) (full text, mbox, link).


Message #70 received at 788963@bugs.debian.org (full text, mbox, reply):

[Message part 1 (text/plain, inline)]
On Sun, 03 Apr 2016 05:04:10 +0200 Tilman Blumenbach <tilman@ax86.net>
wrote:
> Hello,
>
> On Sun, 20 Mar 2016 13:47:59 +0100 Michael Meskes <meskes@debian.org>
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 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 to jessie?

Was just nailed by this one myself.  Lots of users just lost their mailbox
quota.  Is my only solution here to grab quota from stretch?
[Message part 2 (text/html, inline)]

Information forwarded
to debian-bugs-dist@lists.debian.org:
Bug#788963; Package quota.
(Tue, 05 Apr 2016 17:57:04 GMT) (full text, mbox, link).


Acknowledgement sent
to Michael Meskes <meskes@debian.org>:
Extra info received and forwarded to list.
(Tue, 05 Apr 2016 17:57:05 GMT) (full text, mbox, link).


Message #75 received at 788963@bugs.debian.org (full text, mbox, reply):

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 to jessie? 

I'll see what I can to, it seems I misjudged the amount of people that got hit by this. 

Michael
-- 
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL



Bug archived.
Request was from Debbugs Internal Request <owner@bugs.debian.org>
to internal_control@bugs.debian.org.
(Wed, 04 May 2016 07:33:32 GMT) (full text, mbox, link).


Send a report that this bug log contains spam.


Debian bug tracking system administrator <owner@bugs.debian.org>.
Last modified:
Thu Feb 9 16:27:05 2023;
Machine Name:
buxtehude

Debian Bug tracking system

Debbugs is free software and licensed under the terms of the GNU
Public License version 2. The current version can be obtained
from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson,
2005-2017 Don Armstrong, and many other contributors.

Понравилась статья? Поделить с друзьями:
  • Failed to start discovery org bluez error inprogress
  • Failed to start device ar1 error code 40 ensp
  • Failed to start denuvo driver error code 647
  • Failed to start denuvo driver error code 2148204812 wrc 7
  • Failed to start denuvo driver error code 2148204812 total war warhammer 2