DUC displaying incorrect folder information !

[aiamuzz]

Hi,

I am using duc on my Deepin OS ... the information shown in the GUI is incorrect ... it is showing old folders which i have long moved out of the place and the current folders in the same location is nowhere to be seen

the command duc gui /home is giving info that's incorrect ... is there some refresh that's required each time i intend to use the above command ?

thanks for this great utility ... the GUI really helps in identifying the heavy files that devour huge space and we have lost track of them being stored away at a place which we cannot recollect.

hope to see a fix to this issue so i can hunt down those gluttons ... :)

thanks

[aiamuzz]

oh sorry ... didn't realize that duc index needs to be run before each time one intends to visually browse through their folders ...

[aiamuzz]

oh ... seem its indeed a bug ... i ran the command duc index ~ and ran the duc gui /home its is showing the contents that are no longer in the folder ... i just moved it out of that folder a few minutes back ... i ran the 'index' command after i moved that folder ... but he GUI is still showing the folder that was already moved out ...

seems the index command is somehow picking up older folder information ... let me know if you need any info out my affected system ...

[zevv]

Hi,

I'm not sure what your exact problem might be, but a good start to finding out would be to remove the current db (probably ~/.duc.db) and recreate the index.

Quoting aiamuzz (2019-07-06 09:51:50)

oh ... seem its indeed a bug ... i ran the command duc index ~ and ran the duc gui /home its is showing the contents that are no longer in the folder ... i just moved it out of that folder a few minutes back ... i ran the 'index' command after i moved that folder ... but he GUI is still showing the folder that was already moved out ...

seems the index command is somehow picking up older folder information ... let me know if you need any info out my affected system ...

-- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/zevv/duc/issues/216#issuecomment-508905681

-- :wq ^X^Cy^K^X^C^C^C^C

[aiamuzz]

I'm not sure what your exact problem might be, but a good start to finding out would be to remove the current db (probably ~/.duc.db) and recreate the index.

Hello @zevv ... firstly complements are in order ... its a fantastic and visually appealing utility you've built ...

this index command ... is it by design that one has to run it each time one intends to view a particular folder ? ... is it difficult to have this indexing run in the background once we launch duc gui view ?

PS : ... is it possible to have the white background to be transparent ... something similar to how google's picassa viewer used to be a dark transparent space around the image ...

[aiamuzz]

I notice that indexing fails with 'permission denied' error for folders owned by root ... should i be running the indexing command with 'sudo' ... is it safe ?

[zevv]

Quoting aiamuzz (2019-07-06 10:43:52)

I notice that indexing fails with 'permission denied' error for folders owned by root ... should i be running the indexing command with 'sudo' ... is it safe ?

Indexing as root is considered safe, but do realize that the metadata about files which are normally not readably by non-root users ends up in the index.

-- :wq ^X^Cy^K^X^C^C^C^C

[aiamuzz]

Indexing as root is considered safe, but do realize that the metadata about files which are normally not readably by non-root users ends up in the index.

hmmmmm ... haven't reached that stage i guess ...

ran sudo duc index / ... encountered a pile of input/output errors

duc gui /
Path / not found in database
Requested path not found

[zevv]

Quoting aiamuzz (2019-07-06 11:44:22)

Indexing as root is considered safe, but do realize that the metadata about files which are normally not readably by non-root users ends up in the index.

hmmmmm ... haven't reached that stage i guess ...

ran sudo duc index / ... encountered a pile of input/output errors

Check out what is up with the files or directories Duc is trying to scan here. It might be that you are forcing it to index /proc, or maybe you have stale NFS mounts? Worst case your storage is broken and you have actual I/O errors on your disk...

-- :wq ^X^Cy^K^X^C^C^C^C