All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David D. Huff Jr." <David.Huff@computer-critters.com>
To: Vitaly Fertman <vitaly@namesys.com>
Cc: reiserfs-list@namesys.com
Subject: Re: --rebuild-tree, out of disk
Date: Sun, 11 Jan 2004 13:44:32 -0500	[thread overview]
Message-ID: <40019990.8000408@computer-critters.com> (raw)
In-Reply-To: <200401111534.07660.vitaly@namesys.com>

Vitaly Fertman wrote:
> On Sunday 11 January 2004 00:17, David D. Huff Jr. wrote:
> 
>>I've used cfdisk to change change the size of the partition but
>>resize_resierfs fails even when -f is used.
>>
>>Any suggestions on how to minimize space usage?
> 
> 
> Did you want to shrink the partition? Looks like resize_reiserfs failed
> because you run it after the fdisk, it should be run before at shrinking.
> 
> 
>>I'd rather mark the partition clean, then run resize_reiserfs followed
>>by reiserfsck --rebuild-tree but I don't know how.
> 
> 
> I do not undestand you, have you run reiserfsck --rebuild-tree?
> What were your steps in the chronological order?
> 
The system was using an abnormal amount of space, going through 3.8 Gig 
of space in a week that could not be accounted for. I checked directory 
sizes and file sizes, nothing added up to the space being used. It was 
only a webserver and disk growth shouldn't have been more that 35MB a 
month. I ran reiserfsck --check and it said it was OK but I knew it 
wasn't so when I ran --rebuild-tree, it ran out of space.

I'd allocated 2 Gig for swap, so I used cfdisk to reduce it to 1600 Mb 
(/dev/hda2) and deleted and re-allocated the reiserfs partition 
(/dev/hda1) to include the full size. When I run resize_reiserfs -f it 
says to run reiserfsck --rebuild-tree. Well I've done that and received 
the same out of disk condition. -That and using every other switch I can 
think of. I also used gpart but it only recognized /dev/hda2 and that 
there was a 27 Gig partition in front of it, then gpart would abort.

At this point I'm thinking it is de-allocating bad sectors as fast as 
the drive can write.

For my next step I intend to dd the partition to another disk with a 
larger formatted partition and try to run --rebuild tree there.

For your edutainment, that bad disk is one of those IBM Deskstars 
mentioned on the namesys faq I did not know that there was class action 
suit pending in the matter, this is the 4th (Deskstar) drive to die less 
than three years old and on short notice,(all purchased from Jan 2000 
through June 2001, before their evils were known).


  reply	other threads:[~2004-01-11 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10 21:17 --rebuild-tree, out of disk David D. Huff Jr.
2004-01-11 12:34 ` Vitaly Fertman
2004-01-11 18:44   ` David D. Huff Jr. [this message]
2004-01-11 20:27     ` Vitaly Fertman
2004-01-12  4:16       ` David D. Huff Jr.
2004-01-12 10:27         ` Vitaly Fertman
2004-01-14  0:30           ` David D. Huff Jr.

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=40019990.8000408@computer-critters.com \
    --to=david.huff@computer-critters.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vitaly@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.