All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir V. Saveliev" <vs@namesys.com>
To: Cami <camis@mweb.co.za>
Cc: reiserfs-list@namesys.com
Subject: Re: --rebuild-tree
Date: Tue, 06 Jul 2004 12:56:18 +0400	[thread overview]
Message-ID: <40EA6932.7090606@namesys.com> (raw)
In-Reply-To: <40EA5193.2040604@mweb.co.za>

Hello

Cami wrote:
> Hi All,
> 
> Last night i done monthly maintence on all of my
> mailhosts and after doing a reiserfsck, it looks
> like i'll have to rebuild the tree on one of my
> mail clusters (the other 8 clusters were fine)..
> 
> [mailhost01][/root]# df -h
> Filesystem            Size  Used Avail Use% Mounted on
> /dev/emcpowera1       152G   35G  117G  23% /var/spool/virtual
> 
> Can anyone tell me roughly how dangerous this is

it is not dangerous. Just, please, make sure you have recent reiserfsck.

> and roughly how long something like this will take?

hard to say. It depends on hardware. Given that 35 gb is not too much 
reiserfsck --rebuild-tree should not take too much. 2 hours? Vitaly may 
want to correct me, though

> The filesystem stores all the users mailboxes in
> maildir format so there are millions of files..
> 
> Any tips/comments would be appreciated..
> 

PS: please do not forget that backuping is important when dealing with 
user mailboxes even if you are running super reliable hardward and 
bugless software.

> Regards,
> Cami
> 
> 
> 



  reply	other threads:[~2004-07-06  8:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06  6:28 I've done a very bad mistake Andreas Otto
2004-07-06  7:15 ` --rebuild-tree Cami
2004-07-06  8:56   ` Vladimir V. Saveliev [this message]
2004-07-06  9:20     ` --rebuild-tree Cami
2004-07-06 10:22     ` --rebuild-tree Vitaly Fertman

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=40EA6932.7090606@namesys.com \
    --to=vs@namesys.com \
    --cc=camis@mweb.co.za \
    --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.