Your message dated Fri, 30 Apr 2021 15:35:47 +0200
with message-id <E1lcTIn-001M5a-RH@hullmann.westfalen.local>
and subject line Closing this bug
has caused the Debian Bug report #788423,
regarding linux-image-3.16.0-4-amd64: no inode allocation after xfs_growfs
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
788423: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=788423
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Subject: linux-image-3.16.0-4-amd64: no inode allocation after xfs_growfs
Package: src:linux
Version: 3.16.7-ckt9-3~deb8u1
Justification: causes serious data loss
Severity: critical
Tags: upstream

Dear Maintainer,


When extending a lvm volume and then the xfs filesystem with wfs_growfs,
we often encounter "no space left on device" error even with df
reporting a lot of free space and inode.

This seems to be related to this patch :
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9de67c3ba9ea961ba420573d56479d09d33a7587
which is implemented in kernel 3.17.

Remounting the filesystem allow to write data again.


-- Package-specific info:
** Version:
Linux version 3.16.0-4-amd64 (debian-kernel@lists.debian.org) (gcc
version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt9-3~deb8u1
(2015-04-24)

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.16.0-4-amd64
root=UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1 ro quiet
-- 

--- End Message ---
--- Begin Message ---
This bug was filed for a very old kernel. If you can reproduce it with
- the current version in unstable/testing
- the latest kernel from buster.backports
please reopen the bug, see https://www.debian.org/Bugs/server-control

--- End Message ---

Reply via email to