full(4)

💖 FULL — the device that's always full, bestie 💖

okay so this is full(4) from the kernel interfaces girlies, and honestly? she's an icon. a device file so committed to the bit that she's never, ever empty. let's get into it 🫶

---

✨ NAME ✨

full — the always full device. that's it. that's the whole personality. she is full. she stays full. periodt 💅

---

🎀 CONFIGURATION 🎀

so like, if ur system doesn't already have /dev/full chillin' there, don't panic bestie, you can just make it urself with these:

mknod -m 666 /dev/full c 1 7
chown root:root /dev/full

run those and boom, u got a full device of ur very own ✨

---

🦋 DESCRIPTION 🦋

okay so the tea: the file /dev/full has major device number 1 and minor device number 7. write that down, it's giving very specific. 📝

writes to the /dev/full device fail with an ENOSPC error. yes literally every time. no cap. and that's actually the whole point — it's THE way to test how a program handles disk-full errors. like, "does my code panic when the disk is stuffed?" — ask /dev/full, she'll tell u 😭🔥

reads from the /dev/full device will return \0 characters. so it's not gonna give u anything spicy, just a bunch of nulls. lowkey peaceful ngl 🌸

seeks on /dev/full will always succeed. every single time. she never misses 💜

---

🌈 FILES 🌈

• /dev/full — the main character herself 👑

---

⭐ SEE ALSO ⭐

• mknod(1)
• null(4)
• zero(4)

the whole device-file friend group fr fr 🫶

---

and that's the page bestie!! this diva is from Linux man-pages 6.20, dated 2026-02-08, and she goes by full(4) 💖 mwah, go test ur error handling, ily 🎀✨