Buffalo Forums

LS520 with 2x2gb in Raid array.  Upgraded from firmware 3.1(?) to latest 4.10 as the drive indicated the upgrade was available.
All seemed initially well.  The 2 users and admin still present.  The files and 2 shared folders seemed ok when accessed from Windows and Mac.  But then the issues started.
Updating a file (overwriting it) by FTP would fail part way through.
On the Mac, copy a file to a shared folder and the file entry would be created in the directory but the contents of the file would not copy over.  Zero bytes file.
On the PCs, trying to copy a file into the share folder and the copy fails with "There is not enough space on <directory>"
On the NAS web interface file copy will just fail.

I can read files OK, but the drive is now acting as though it is full.  Not the same as read only as the directory can be updated, but simply can't add or update files.

Just to be clear, the drive is not full!  241Gb free of 1.78Tb

Please help!

---- Update ----
It seems a quota has been applied, if I go by an error in FTP:  552 Transfer Aborted. Disk quota exceeded

There were no quota's applied before the update to 4.10

Also:  A new share called 'homes' has appeared along side our existing shares.  Inside 'homes' are the files from our primary share 'beau'.

Really don't understand why quotas should have been applied.  I can't see a way to remove them.  Any help?
---- Update 2 ----
Had to use the Reset function from the admin applications menu.
Once reset, the quota problem was no more.  However, all users and user folders are deleted, therefore YOU WILL NEED TO BACKUP FULLY BEFORE PERFORMING 'reset'.  I had a backup on another NAS, so I am in the process of restoring data as I update this entry.
In my case, only the Public folder was preserved, and this was apparently because I did not change the RAID configuration as part of the reset.

=== Lessons for those upgrading from 3.1 to 4.10 :-
If you can, use the web interface for each user to move (cut and past using the web interface) the user files from user folders and shares into temporary folders in the Public share.  There's a chance files in Public won't get deleted on reset, saving huge restores times.
Having reset the unit you will need to re-input users and groups, and setup and shared folders again.
You should now have your shares and user folders back, but empty.  If you did the cut and paste to Public process as above, then it's a matter of using the web interface for each user to cut and paste the relevant files back into their correct locations.  Otherwise restore from backup.
The newly set up users and share do not seem to have the quota limitation I originally had after first upgrading to 4.10 (hooray!)

--- My thoughts ? ---
At the very least this is a poor 'documentation bug'. The preparation steps to preserve data should be outlined and the quota mode should be described.
It is also possible that there is a bug to do with migrating user names and folders.  In the 4.10 environment you are not allowed to have a username that matches an existing share folder and vice-versa.  But when you create a user in 4.10 you then it creates a user share of that same name.  This seemed to create a clash when migrating / upgrading from 3.1x to 4.10.  I suppose v4.10's way of handling the situation was to impose a quota and force a reset / rebuild once backed up.

I hope this helps others.

Experiencing the same problem with a new folder called 'homes'.  It appeared after upgrading my LS520 to FW 4.10. Inside 'homes' are all the files from my primary user,  but for me it is not a shared folder, probably due to the primary user is not a shared folder.

So far, I have no issues with "There is not enough space"

Any one know if it is possible to downgrade to 3.10 again?

Quote from: mbpilot on December 16, 2016, 02:58:46 PM
Experiencing the same problem with a new folder called 'homes'.  It appeared after upgrading my LS520 to FW 4.10. Inside 'homes' are all the files from my primary user,  but for me it is not a shared folder, probably due to the primary user is not a shared folder.

So far, I have no issues with "There is not enough space"

Any one know if it is possible to downgrade to 3.10 again?

It seems the "homes" share is actually a synonym (symbolic link?) for the user folder that you logged into the Buffalo with.  So if you log in with user John, then homes represents the John user folder/share.  If you log in as Mary then homes is Mary's stuff.  You have the option of connecting to the homes directory or the user directory as they are both simultaneously available.  The presence of "homes" folder creates a convenience in directory naming for some situations. 

Hi I have a similar situation.  I suddenly got the message on my Mac - not enough disk space.  Help please?