From: Thomas <c.monty@web.de>
To: linux-btrfs@vger.kernel.org
Subject: Issue: errno:28 (No space left on device)
Date: Tue, 9 Aug 2016 11:09:24 +0200 [thread overview]
Message-ID: <a5c1aaee-1dfe-9c01-fcf8-129db266aa90@web.de> (raw)
Hello!
I'm facing a severe issue with Debian installation using BTRFS:
errno:28 (No space left on device)
After a few minutes of system usage I get this error message for any
action, means there's really no disk space left.
However, the output of btrfs fi usage / reports that ~10% of disk space
should be free.
I have 2 questions:
1. Why is the OS reporting an error "Issue: errno:28 (No space left on
device)" whereas "btrfs fi usage" reports free space?
2. How can I solve this issue w/o the possibility of extending the
partition?
THX
---------------------------------------------------------------------------------------
thomas@pc8-nb:~$ uname -a
Linux pc8-nb 4.6.1-towo.1-siduction-amd64 #1 SMP PREEMPT siduction 4.6-1
(2016-06-04) x86_64 GNU/Linux
thomas@pc8-nb:~$ sudo btrfs --version
btrfs-progs v4.5.2
thomas@pc8-nb:~$ sudo btrfs fi usage /
Overall:
Device size: 20.53GiB
Device allocated: 20.53GiB
Device unallocated: 0.00B
Device missing: 0.00B
Used: 18.25GiB
Free (estimated): 1.96GiB (min: 1.96GiB)
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 160.00MiB (used: 400.00KiB)
Data,single: Size:19.76GiB, Used:17.81GiB
/dev/sda8 19.76GiB
Metadata,single: Size:776.00MiB, Used:455.73MiB
/dev/sda8 776.00MiB
System,single: Size:4.00MiB, Used:16.00KiB
/dev/sda8 4.00MiB
Unallocated:
/dev/sda8 0.00B
thomas@pc8-nb:~$ sudo btrfs fi show
Label: 'siduction' uuid: dbb9433e-a84f-4e84-9200-49350b31a3f6
Total devices 1 FS bytes used 18.25GiB
devid 1 size 20.53GiB used 20.53GiB path /dev/sda8
thomas@pc8-nb:~$ sudo btrfs su li /
ID 257 gen 5498245 top level 5 path @
ID 258 gen 5498245 top level 5 path @home
ID 259 gen 5488356 top level 5 path @tmp
ID 260 gen 2029641 top level 5 path @var_lib_lxc
ID 261 gen 5480763 top level 5 path @var_log
ID 262 gen 5467204 top level 5 path @var_spool
ID 263 gen 5467205 top level 5 path @var_tmp
ID 290 gen 5464299 top level 257 path .snapshots
ID 291 gen 2026169 top level 258 path @home/.snapshots
ID 293 gen 2029641 top level 260 path @var_lib_lxc/.snapshots
ID 355 gen 163972 top level 290 path .snapshots/17/snapshot
ID 356 gen 167205 top level 290 path .snapshots/18/snapshot
ID 357 gen 5383634 top level 5 path @var_cache_apt_archives
ID 358 gen 5464163 top level 290 path .snapshots/19/snapshot
thomas@pc8-nb:~$ sudo journalctl | grep space
[...]
Jun 16 17:52:39 pc8-nb unattended-upgrade-shutdown[13530]: OSError:
[Errno 28] No space left on device
Jun 16 17:52:39 pc8-nb unattended-upgrade-shutdown[13530]: OSError:
[Errno 28] No space left on device
Jun 16 17:52:39 pc8-nb unattended-upgrade-shutdown[13530]: OSError:
[Errno 28] No space left on device
[...]
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://ftp.fau.de/debian/dists/stable/main/Contents-i386 Write error -
write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://debian.mirror.lrz.de/debian/dists/stable/contrib/binary-i386/Packages.gz
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://debian.mirror.lrz.de/debian/dists/stable/contrib/i18n/Translation-en
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://debian.mirror.lrz.de/debian/dists/stable/contrib/Contents-amd64
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://debian.mirror.lrz.de/debian/dists/stable/contrib/Contents-i386
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://mirror.unitedcolo.de/debian/dists/stable/non-free/binary-amd64/Packages.gz
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://mirror.unitedcolo.de/debian/dists/stable/non-free/binary-i386/Packages.gz
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://debian.mirror.lrz.de/debian/dists/stable/non-free/i18n/Translation-en
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://mirror.unitedcolo.de/debian/dists/stable/non-free/Contents-amd64
Write error - write (28: No space left on device)
Jul 17 04:43:02 pc8-nb cron-apt[2658]: E: Failed to fetch
http://ftp.fau.de/debian/dists/stable/non-free/Contents-i386 Write
error - write (28: No space left on device)
[...]
next reply other threads:[~2016-08-09 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-09 9:09 Thomas [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-09 11:50 Issue: errno:28 (No space left on device) Thomas
2016-08-09 12:21 ` Tomasz Torcz
2016-08-09 12:56 ` Austin S. Hemmelgarn
2016-08-09 13:39 ` Noah Massey
2016-08-09 13:56 ` Roman Mamedov
2016-08-09 13:47 ` Josef Bacik
2016-08-09 9:06 Thomas
2016-08-09 16:50 ` Chris Murphy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5c1aaee-1dfe-9c01-fcf8-129db266aa90@web.de \
--to=c.monty@web.de \
--cc=linux-btrfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).