From: gentoo@depardo.ch
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] OT: disk full but lot of space
Date: Mon, 8 Aug 2005 12:59:06 +0200 [thread overview]
Message-ID: <200508081259.06214.gentoo@depardo.ch> (raw)
Hello,
This is OT, but I'm kind of worried and google hasn't been my friend...
* I'm doing backups of my server everynight and had the following errors in
the mail from the cron output this morning. repeated a dozen of times.
bzip2: I/O or other error, bailing out. Possible reason follows.
bzip2: No space left on device
Input file = (stdin), output file = (stdout)
/local/sbin/mk-rs-backups.sh: line 26: 22516 Broken pipe $TAR cjf
$DSTDIR/site-$site.tar.gz $name
bzip2: I/O or other error, bailing out. Possible reason follows.
bzip2: No space left on device
Input file = (stdin), output file = (stdout)
tar: Child returned status 1
tar: Error exit delayed from previous errors
* checking my logs I found the following error repeating ~6000 times.
Aug 8 03:17:00 www kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block:
block(14366126) >= blocks count(14366126) - block_group = 438, es == c2510400
[...]
Aug 8 08:46:52 www kernel: EXT3-fs error (device ide0(3,2)): ext3_new_block:
block(14372149) >= blocks count(14366126) - block_group = 438, es == c2510400
"df" is telling that my disk is only half full: ~28Gb free.
"df -i" is reporting only ~2% inodes used.
"tune2ds -l" follows
So... is my disk broken? my fs corrupted? While is ext3 trying to allocate a
block with a higher count than the max?
Any help welcomed, thanks in advance.
[root@www log]# /sbin/tune2fs -l /dev/hda2
tune2fs 1.26 (3-Feb-2002)
Filesystem volume name: /
Last mounted on: <not available>
Filesystem UUID: <none>
Filesystem magic number: 0xEF53
Filesystem revision #: 1 (dynamic)
Filesystem features: has_journal filetype needs_recovery sparse_super
Filesystem state: clean with errors
Errors behavior: Continue
Filesystem OS type: Linux
Inode count: 7192576
Block count: 14366126
Reserved block count: 718306
Free blocks: 11154684
Free inodes: 7060644
First block: 0
Block size: 4096
Fragment size: 4096
Blocks per group: 32768
Fragments per group: 32768
Inodes per group: 16384
Inode blocks per group: 512
Last mount time: Wed Feb 23 20:49:57 2005
Last write time: Mon Aug 8 08:46:52 2005
Mount count: 22
Maximum mount count: -1
Last checked: Wed Nov 20 03:44:33 2002
Check interval: 0 (<none>)
Reserved blocks uid: 0 (user root)
Reserved blocks gid: 0 (group root)
First inode: 11
Inode size: 128
Journal UUID: <none>
Journal inode: 8
Journal device: 0x0000
First orphan inode: 6488266
--mat
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2005-08-08 11:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:59 gentoo [this message]
2005-08-08 11:28 ` [gentoo-user] OT: disk full but lot of space Christoph Gysin
2005-08-08 11:55 ` gentoo
2005-08-08 12:10 ` Christoph Gysin
2005-08-08 12:40 ` gentoo
2005-08-08 12:56 ` Christoph Gysin
2005-08-08 13:53 ` gentoo
2005-08-08 14:05 ` Christopher Fisk
2005-08-08 22:14 ` Raymond Lillard
2005-08-12 22:46 ` mat
2005-08-08 14:50 ` Hans-Werner Hilse
2005-08-08 19:10 ` Jonathan Nichols
2005-08-08 11:57 ` Norberto Bensa
2005-08-08 12:09 ` gentoo
2005-08-08 12:09 ` Christoph Gysin
2005-08-08 13:54 ` Christopher Fisk
2005-08-09 2:17 ` Norberto Bensa
2005-08-09 11:26 ` Christoph Gysin
2005-08-14 7:30 ` Norberto Bensa
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=200508081259.06214.gentoo@depardo.ch \
--to=gentoo@depardo.ch \
--cc=gentoo-user@lists.gentoo.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