files disapear after fsck [RESOLVED]

[modem7]

Hey guys,

If I move files from var/hda/files/downloads to var/hda/files/anime and then do an fsck, the files inside the folder of /anime disappear.

Any ideas?

Could it be because /var/hda/files is my LZ (and not pooled)?




Many thanks!

[bigfoot65]

What do you mean disappear? Are there symlinks left behind? Also is this move being done from a client via Samba or directly on the HDA?

[modem7]

What do you mean disappear? Are there symlinks left behind? Also is this move being done from a client via Samba or directly on the HDA?

If I move var/hda/files/downloads/HorribleSubs_One_Piece_-_543_360p_mkv which has 3 files inside to var/hda/files/anime/HorribleSubs_One_Piece_-_543_360p_mkv

then do a fsck, the folder structure stays (so HorribleSubs_One_Piece_-_543_360p_mkv folder is there) but there are no files inside it.

I'm doing this via the gui (via VNC)

I'm not sure how to check for symbolic links? (apologies)

Many thanks!

[bigfoot65]

Ok, so your are moving a folder with files on the HDA then. Did you enable mount shares locally with Greyhole?

http://wiki.amahi.org/index.php/Mount_Shares_Locally

This is the warning on the wiki page:

Important Warnings
You should never change or delete files in the shared directories (/var/hda/files/* by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the Uses pool option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should Mount Shares Locally.

You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using greyhole --fsck). Until then, your new files will be stored in your shared directories (normally /var/hda/files/share_name/).

Also, touching anything inside the gh directories that Greyhole creates at the root of your partitions is a recipe for disaster.

When you mess with files in shares on the HDA, you need to have this running.

[modem7]

Ok, so your are moving a folder with files on the HDA then. Did you enable mount shares locally with Greyhole?

http://wiki.amahi.org/index.php/Mount_Shares_Locally

This is the warning on the wiki page:

Important Warnings
You should never change or delete files in the shared directories (/var/hda/files/* by default) directly on the HDA, using the terminal, or the Gnome file browser, for the shares for which you checked the Uses pool option in the Amahi dashboard. If you want to work with files on Greyhole shares on the HDA, you should Mount Shares Locally.

You should be safe reading existing files directly, or adding new files directly, as long as don't care that your new files will only be moved into the storage pool during the next check, which runs automatically at midnight (or manually using greyhole --fsck). Until then, your new files will be stored in your shared directories (normally /var/hda/files/share_name/).

Also, touching anything inside the gh directories that Greyhole creates at the root of your partitions is a recipe for disaster.

When you mess with files in shares on the HDA, you need to have this running.

Yupyup, all locally mounted.

What I *HAVE* done however, is enabled disk-cache in the BIOS, this SEEMS to be giving me good write speed for now.

I'll keep monitoring, and hopefully everything will be A-OK.

Thank you very much for this! Helpful as always BigFoot.