From: Oleg Drokin <green@namesys.com>
To: JPASTORM@esade.edu
Cc: reiserfs-list@namesys.com
Subject: Re: journal log file
Date: Sun, 26 May 2002 11:25:22 +0400 [thread overview]
Message-ID: <20020526112522.B11674@namesys.com> (raw)
In-Reply-To: <OF171252DB.A2293F71-ONC1256BC4.003AE364@esade.edu>
Hello!
On Sat, May 25, 2002 at 12:59:40PM +0200, JPASTORM@esade.edu wrote:
> After the mkreiserfs and mount commands so as to convert ext2 partitions
> into reisrerfs, I noticed some diferences between the du and df commands
> output.
> [root@apollo /var]# df
> Filesystem 1k-blocks Used Available Use% Mounted on
> /dev/sda5 7168784 1637808 5530976 23% /cache
> /dev/sda6 461788 145536 316252 32% /var
> [root@apollo /cache]# du
> 1591088 .
33*1024(journal size + some reserved space)+1591088 = 1624880
and 16k were probably occupied by internal tree nodes, that are not
accounted for files, so du do not show this.
> [root@apollo /var]# du
> 114596 .
33*1024+114596 = 148388
Here we see that actual number of bytes is less than we expected.
This is because of tail packing and du's feature.
du only takes into account amount of block each file occupies.
So if two files occupy the same block, du would count amount of blocks
used to be 2, where correct amount is 1 (tail packing).
Probably you have some amount of small files on your /var partition.
(smal files are files that are less than 16K in size).
> The df value for /var partition was more or less expected having in count
> these 32 MB of the journal. Could you explain me the difference in the
> /cache partition (it's just the squid cache partition)?
I do not see much difference, in fact.
> I also understand that I cannot make a reiserfs partition from an ext2
> partition if I have less than these 32 MB left in it and I want to preserve
> all data.
There is no transparent tool to convert ext2 fs to reiserfs.
The current procedure is to backup all the data, reformat the partition,
and then to restore the data back.
And yes, the 33M would be claimed for journal and some other internal to
filesystem stuff.
Also it is highly advisable to have at least 10% of free space on the partition,
so that large-scale fragmentation would less likely to occur.
Bye,
Oleg
next parent reply other threads:[~2002-05-26 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF171252DB.A2293F71-ONC1256BC4.003AE364@esade.edu>
2002-05-26 7:25 ` Oleg Drokin [this message]
2002-05-20 14:02 journal log file Dieter Nützel
2002-05-20 14:07 ` Chris Mason
2002-05-20 14:45 ` Oleg Drokin
2002-05-20 14:52 ` Dieter Nützel
-- strict thread matches above, loose matches on Subject: below --
2002-05-18 10:30 JPASTORM
2002-05-20 6:15 ` Oleg Drokin
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=20020526112522.B11674@namesys.com \
--to=green@namesys.com \
--cc=JPASTORM@esade.edu \
--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.