All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Zarochentsev <zam@namesys.com>
To: Jake Hawkes <jake@infinitylimited.net>
Cc: reiserfs-list@namesys.com
Subject: Re: shrink reiserfs
Date: Sun, 23 Jan 2005 22:49:18 +0300	[thread overview]
Message-ID: <20050123194918.GI10921@backtop.namesys.com> (raw)
In-Reply-To: <18682.62.135.89.53.1106507496.squirrel@mail.infinitylimited.net>

On Sun, Jan 23, 2005 at 12:11:36PM -0700, Jake Hawkes wrote:
> Alex Zarochentsev said:
> > On Sun, Jan 23, 2005 at 10:49:56AM -0700, Jake Hawkes wrote:
> >> Alex Zarochentsev said:
> >> > Hello,
> >> >
> >> > On Sun, Jan 23, 2005 at 08:48:14AM -0700, Jake Hawkes wrote:
> >> >> Hi.
> >> >>
> >> >>  resize_reiserfs says that there are already too many allocated
> >> blocks.
> >> >
> >> > which resize_reiserfs command produces the error message?
> >>
> >> resize_reiserfs -v -s -1G /dev/hda4
> >>
> >> and when that failed, I tried
> >>
> >> resize_reiserfs -v -s -1M /dev/hda4
> >
> > and it failed too?
> 
> yep
> 
> 
> >
> > which reiserfsprogs version are you using?  It is possible
> > that this bug is fixed already in the latest release of
> > reiserfsprogs (3.6.19).
> 
> jacobh log # esearch reiserfsprogs
> [ Results for search key : reiserfsprogs ]
> [ Applications found : 1 ]
> 
> *  sys-fs/reiserfsprogs
>       Latest version available: 3.6.19
>       Latest version installed: 3.6.18
>       Size of downloaded files: [no/bad digest]
>       Homepage:    http://www.namesys.com/
>       Description: Reiserfs Utilities

yes, it see, new reiserfsprogs has this bug (v3.0.9 does not :-/) .

As a workaround  I suggest don't use relative values in current resizer.
please try resize_reiserfs -v -s 21G /dev/hda4 .

> I'm using 3.6.18

Thanks for the report.

-- 
Alex.

  parent reply	other threads:[~2005-01-23 19:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-23 15:48 shrink reiserfs Jake Hawkes
2005-01-23 17:11 ` Alex Zarochentsev
     [not found]   ` <18298.62.135.89.53.1106502596.squirrel@mail.infinitylimited.net>
2005-01-23 19:07     ` Alex Zarochentsev
2005-01-23 19:11       ` Spam
     [not found]       ` <18682.62.135.89.53.1106507496.squirrel@mail.infinitylimited.net>
2005-01-23 19:49         ` Alex Zarochentsev [this message]
2005-01-23 21:23           ` Alex Zarochentsev
2005-01-23 21:53             ` Jake Hawkes
2005-01-24  6:46               ` David Masover
     [not found]               ` <41F64DA7.2070502@nauticom.net>
2005-01-28 15:52                 ` Jake Hawkes
2005-01-30  0:42                   ` David Masover
2005-01-30 17:25                     ` Jake Hawkes

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=20050123194918.GI10921@backtop.namesys.com \
    --to=zam@namesys.com \
    --cc=jake@infinitylimited.net \
    --cc=reiserfs-list@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.