I am using debian unstable 64 bit with lvm and ext3. All options are default. How did I find out? This OS is a VM. And the disk data is in a non-fixed size file, not compressed. Sorry I forgot how to say this in English, by non-fixed size, I mean the VM software just allocate the actual disk space that has data to write. And I think this is not just about ext3, but ext3 & 64bit. Because with the same environment, 32bit works fine for this process.
On Mon, Jun 28, 2010 at 10:54 PM, H.S. <[email protected]> wrote: > On 27/06/10 10:51 PM, Magicloud Magiclouds wrote: >> Thank you guys. >> I have not follow Stephen's guide, but I figured the reason out. It >> seems like an ext3's fault. The space (i-node wise) was used 5.x GB, >> but the actual space (data wise) was used only 1 GB. So a lot of space >> was just empty and wasted. > > I experience the same thing some weeks ago (had to use a different > machine with a larger hard disk to get the job done). It is interesting > to note that you think that ext3 is at fault here. How did you find that > out? I would like to know whether it is a problem with ext3 at this time > in Unstable. > > > -- > > Please reply to this list only. I read this list on its corresponding > newsgroup on gmane.org. Replies sent to my email address are just > filtered to a folder in my mailbox and get periodically deleted without > ever having been read. > > > -- > To UNSUBSCRIBE, email to [email protected] > with a subject of "unsubscribe". Trouble? Contact [email protected] > Archive: http://lists.debian.org/[email protected] > > -- 竹密岂妨流水过 山高哪阻野云飞 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
