Okay, I processed that statement and I don't see the PHP Warning any longer after several checks of the greyhole.log... So, that's positive... I'm still seeing the 90k transactions warning, so there must be a whole bunch of records left to process.. Guess I'll just let it run and see what happens... What seems to have been the problem on that one?
On another note, I've got a question... Would this issue have affected any hard data I migrated to the samba shares earlier today when this issued occurred? Here's an example of how I migrated data: "rsync -avzru /mnt/windows/DE/shares/movies/ /mnt/samba/movies/"
What throws me is going into /mnt/samba/movies and not seeing any data... I can understand symlinks not being there and thus not seeing data... but what about data I was rsync'ing in via the above command while this issue was occurring? Doesn't it sit on the LZ drive in /var/hda/files/movies for example till it pushes it out to /var/hda/files/drives/drive1/gh/movies? Is it possible it never got pushed out to the second path and was deleted along with the symlinks?
jbmia
Data in shares missing (or not displaying)
Re: Data in shares missing (or not displaying)
Having a high count of transactions if fine.
That message about 90k queued tasks is just information, it tells you it will work on those tasks before looking further to see if there's more tasks to do (which I'm sure there is).
Whatever happened to your symlinks, it's entirely possible it also happened to your real files that was in the same directory, waiting to be processed, so yes, those could have been deleted along with your symlinks, effectively deleting your data before it could be added into your storage pool.
I'd wait for greyhole to finish processing what it has now, then do another --fsck just to be sure, then re-do a rsync to see if there are files missing. Files already there wouldn't be copied again, just any files that would be missing.
That message about 90k queued tasks is just information, it tells you it will work on those tasks before looking further to see if there's more tasks to do (which I'm sure there is).
Whatever happened to your symlinks, it's entirely possible it also happened to your real files that was in the same directory, waiting to be processed, so yes, those could have been deleted along with your symlinks, effectively deleting your data before it could be added into your storage pool.
I'd wait for greyhole to finish processing what it has now, then do another --fsck just to be sure, then re-do a rsync to see if there are files missing. Files already there wouldn't be copied again, just any files that would be missing.
- Guillaume Boudreau
Re: Data in shares missing (or not displaying)
Thanks... will do...
To clarify on the 90k thing, I was really more asking about the PHP warning error and the fix we applied in MySQL... Can you fill me in on what was going on there and what we fixed? Just so I can understand a bit more?
Thanks again for being there!
jbmia
To clarify on the 90k thing, I was really more asking about the PHP warning error and the fix we applied in MySQL... Can you fill me in on what was going on there and what we fixed? Just so I can understand a bit more?
Thanks again for being there!
jbmia
Re: Data in shares missing (or not displaying)
The warning was caused by a too small column in the database.
The current maximum size is set to 255 characters, but you value was bigger than that.
Upcoming versions of GH will increase the size of that database field, to prevent this from happening in the future.
The current maximum size is set to 255 characters, but you value was bigger than that.
Upcoming versions of GH will increase the size of that database field, to prevent this from happening in the future.
- Guillaume Boudreau
Who is online
Users browsing this forum: No registered users and 11 guests