problems with nss6000 and the integrated backup function

Unanswered Question

I have a nss6000 with 4 x seagate 750GB configured as raid 5.

I upgrade them to 1.14 in July and everything is up and running, with one exception, the backup.


Everytime i start a backup i receive the message that there is no space left on

destination. Sometimes after 1GB and sometimes it grow up to 5 GB but then

the error occurs.


I try the options "local file system" and "remote cifs filer" but on both

i receive the error.


There is enough space left, and i try different backup targets, but every time the

same error message.


regards

juergen

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Today i try again a backup, the target was a NSS6000 and here is the logfile:


--------------------------------------

2009-10-04 12:46:05 The last NAS Shutdown was not clean
2009-10-04 11:13:56 Backup .autohome to backup/backup/NAS0018f8055b1f..autohome_Backup_2009.10.03_20.09.08.tar.gz; No space left on destination
2009-10-03 20:09:08 Backup home to backup starting
2009-10-03 20:08:37 Backup .autohome to allgemein/backup/NAS0018f8055b1f..autohome_Backup_2009.10.03_20.07.29.tar complete
2009-10-03 20:07:29 Backup home to allgemein starting

--------------------------------------


the files to backup was about 60 GB and the backupfile grows up to this 60GB and

than the NSS6000 shut down, the temperatures are around 38 degrees (we have air conditioning  in this room)


...so any ideas where is the problem?

Alejandro Gallego Thu, 10/08/2009 - 15:27
User Badges:
  • Cisco Employee,

Just want to make sure I am understanding the problem.

You performing a back up from the NSS to a remote CIFS location. You are attempting to back up 60GB to the remote location but the back up fails. Is this correct?

Once the back up completes, the NSS reboots without being told to do so.

Please let me know if this discribes your problem.

David Carr Fri, 10/16/2009 - 12:42
User Badges:
  • Silver, 250 points or more

What version of firmware are you using on your nss6000?

organodomi Tue, 10/20/2009 - 02:12
User Badges:

Hi I have exactly the same problem with my configuration:

We have an NSS4000 - 4 x 1Tb WD disks.

Bay 1 & 2 setup as RAID 1, Bay3 and Bay4 setup as simple normal disks.

I have a share on my Raid 1 disks called Meletes which I try to backup to Disk 3 (Bay3).

The share used space is approx 50Gb and the Disk 3 free space more than 900Gb.

The message I get is:


2009-10-02 13:00:49 Backup meletes to normal_bcp/backup/DATASERVER.meletes_Backup_2009.10.02_00.15.05.tar.gz; No space left on destination
2009-10-02 00:15:05 Backup meletes to normal_bcp starting


Result is the same no matter if I use compression or not.

Firmware is 1.14-20, and the system is connected to a network though a AD Domain.

I would really appriciate any help, thank you.

Alejandro Gallego Tue, 11/03/2009 - 14:30
User Badges:
  • Cisco Employee,

In your earlier post you showed the following log entries:


2009-10-04 12:46:05 The last NAS Shutdown was not clean
2009-10-04 11:13:56 Backup .autohome to backup/backup/NAS0018f8055b1f..autohome_Backup_2009.10.03_20.09.08.tar.gz; No space left on destination
2009-10-03 20:09:08 Backup home to backup starting
2009-10-03 20:08:37 Backup .autohome to allgemein/backup/NAS0018f8055b1f..autohome_Backup_2009.10.03_20.07.29.tar complete
2009-10-03 20:07:29 Backup home to allgemein starting


The part that I am interested in is this "Backup .autohome to allgemein/backup/NAS0018f8055b1f"  I am inclined to say that the "home" directory for your users is not set. If you look under "Access > Options" what does does the location say for "Home Directory Location"?

I tried to backup only the share "allgemein" with the same results:


2009-11-10 09:44:10 The last NAS Shutdown was not clean
2009-11-10 09:19:47 Backup allgemein to mgcbackup/backup/NAS0018f8055b1f.allgemein_Backup_2009.11.09_23.25.57.tar.gz; No space left on destination
2009-11-09 23:25:57 Backup allgemein to mgcbackup starting


regards

juergen

Alejandro Gallego Tue, 11/10/2009 - 13:49
User Badges:
  • Cisco Employee,

Now I see in your log that the NSS was abruptly shutdown. Did it become unresponsive once the backup failed?

On the bright side, I have been able to replicate this problem but I still need more time to find the cause and possible resolution. Could you post a screenshot of your Volumes page?

Apexrp2009 Thu, 11/12/2009 - 05:24
User Badges:

Hallo,


I had the same issue almost half a year ago, and CISCO is still working on the solution. No workaround has been provided.

If you want more info about my problem please see the thread at the other CISCO forum


http://forums.linksysbycisco.com/linksys/board/message?board.id=Network_Storage&thread.id=6346


In general the problem is caused by too many files in one share. The size of the files should not matter. I have tested it on NSS4000 and NSS6000 with 750GB HDD with RAID1, RAID10, and NO RAID. The problem was always the same. I have also tried to backup from one NSS to another (from 4000, to 6000 and from 6000 to 4000), on the same NSS but to another share (on both 4000 and 6000), to a shared folder on a Windows based workstation. The result was always the same "no space left on destination", although, there was plenty of free space.


Oh, I have forgotten to add what files have I tested. I have just taken the "inf" folder from the Windows directory and copied it many times (20-30). It resulted in thousands of files in one directory with a quite small size (about 1GB).


The engineers in CISCO had some problems with replicating my issue, but as far as I know they have finally managed to do so. Moreover, they have checked that it is highly propbably that the previous firmware also had the same issue, but they have not confirmed it, yet.


--

Kind regards,

Marcin

Yes it become unresponsive and u can find a screenshot of the volumes on this url:


http://www.imgimg.de/bild_nss60002f80db73jpg.jpg.html


i find no entrys in the cifs log but i wonder why in the cifs log are so many

errors - there are in 30 days 403.000 entrys ...and the most of them are errors.


i know that cisco is the specialist for networks, but in this case i think they make

a big mistake to buy linksys and their faulty storages. i can't count the hours i

hang around on the phone at linksys hotlines with the result that they dont

can resolve any problem.


this is a 2 year old device, and after two years there are still a lot of bugs.

if this device is a netgear or dlink, i will expect the problems, but cisco?


i'm sad about the money for our 2 nss6000, and i dont think that i will buy

a storage from cisco again.


regards

juergen

Alejandro Gallego Thu, 11/12/2009 - 13:41
User Badges:
  • Cisco Employee,

Juergen,


With the work that I have been doing it looks like I may have a workaround, but I am still looking at this. With the above post, that information has been really helpful. If you have not yet called Cisco Support please do so and get a case created. This is very important that we document this problem.


Alejandro

daviddun Wed, 02/24/2010 - 09:09
User Badges:
  • Bronze, 100 points or more

Good Afternoon,


I wanted to follow on this posting to see if anybody was able to resolve the issue posted.


Please let me know a case # to reference or workaround needed to resolve the issue.

Actions

This Discussion