On Sexta 29 Agosto 2008 11:23:45 macintoshzoom wrote: > > <macintoshzoom@xxxxxxxxxxx> wrote: > >> BUT Konqueror was unable to tell me about that, this is an issue to me. > >> When requesting Konqueror about used space (properties) of each folder > >> it doesn't recognize that there are some GB of space that are not really > >> occupied, but only are from the same file but hard linked to different > >> subfolders. > > > > The problem is that you cannot tell two file entries are actually the > > same file unless you look at both entries and compare the inodes. To > > tag hard-linked files, konqueror would have to scan the whole > > filesystem. > > To make konqueror regularly or by demand "scan the whole filesystem" is > possible? Everything is possible. The question is not that. The question is if it's worth doing it. > Is that a hard task? I have a porwerful box, and I'm not > afraid about hard tasks. It's a very hard task. You need to scan the entire filesystem. That means something between ten minutes to an hour of intense disk I/O. All your memory caches will be thrown away. Performance will be extremely lousy while that task is running as well as just after it. Not to mention that intense I/O is a laptop battery killer. More drawbacks: - if you don't update often enough, you won't see the latest changes - you may *still* not find all other links to a given inode > > Whit 'ls' you can ask to see the inode number associated with the > > file, and thus you could determine if two file entries point to the > > same blocks; Konqueror does not have a way to display the information, > > not even in the detailed view; but that information is rarely needed. > > Yes it's rarely needed, as many other things that are anyway already > implemented for a total control of what happens in your system. I think I use ls -i at most once per year. You *definitely* don't want a periodic task to do that in Konqueror. And maybe you don't want that functionality at all: if you really need to know about inodes, you should use ls and du. > And I want to know why it's storing those GB files hard-linked to > different subfolders (in such way that I can't know via standard KDE > tools what is the real space left free on my box, that this is YES a > matter of issue for me. Like I said in the other email, disk space calculation needs to take inodes and hardlinks into consideration. That's a bug if they don't. -- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org PGP/GPG: 0x6EF45358; fingerprint: E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
Attachment:
signature.asc
Description: This is a digitally signed message part.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<