D-Link Forums
The Graveyard - Products No Longer Supported => D-Link Storage => DNS-321 => Topic started by: sholland on November 23, 2009, 11:58:44 AM
-
We have a 2 week old DNS-321 NAS which seems to be having problems. Network setup: DIR-625 router (DNS plugged into that), 2 XP machines, and 1 Windows 7 machine.
After doing some trouble shooting, I've determined that it works well after being unplugged and then plugged back in (the off switch does not seem to work - if I hold it down long enough it starts flashing, but then nothing else happens even after being left for an hour).
At that point, I can access the NAS, and the read/write file access time is comparable to reading/writing to shared directories on the other computers.
However, after being on for a while, it gets slower and slower. Logging into the admin for the NAS also gets slower and slower, to the point of not being able to log in. It gets so slow as to be unuseable, so unless I was rebooting it hourly (or sooner), it would be unuseable.
Some details of the setup:
DHCP Client is on, jumbo frames off, DHCP server off, UPNP server off, firmware is latest, power management now set to HDD hibernation disabled (changed on Friday, doesn't seem to have affected anything), DDNS disabled, ftp server off.
Any suggestions highly appreciated!
Sarah
-
Is it slow accessing it from another machine as well?
-
Yes, it is slow accessing it from all 3 machines. (sorry, forgot to mention that before).
-
Have you performed any speed tests for actual throughput for both after you cycled power and then say a few hours later, or whenever you deem it slow? Also, I'd be curious to know what your network adapter throughput is for Bytes Total, Bytes Sent, Bytes Recieved and tell us what if any operations you are performing such as reading a large file or writing a large file.
Also, how is your NAS set up? RAID 0, RAID 1, Seperate Disks? What model drives do you have installed?
Did you flash to the lasest firmware (verison 1.03) and clear the settings to default? One other thing you could try so long as you don't have hatachi drives and/or EXT3 format, try a previous flash version to see if the problem goes away.
If you didn't state this was linked to power cycling the NAS, I'd have said you have lots of traffic on your network. Because you say you can't hold down the power button and turn off the device, I'm thinking the firmware is not working properly or you have bad hardware.
Since it's only 2 weeks of age, seriously think about returning it for a replacement.
Last thought is remove your drives, set to factory defaults, download a fresh copy of version 1.03, reflash. Now set up the NAS again as you had before (do not use a backup of the configuration to restore it, do it by hand). Install your drives and see if it works.
Seriously, this is an odd problem. Good luck and report back what you do.
-
I'm so relieved to hear this is an odd problem - I was beginning to think I was missing something very important!
The drives are Western Digital, I believe - don't have the model #s handy. Raid 1, nothing shows as an error for them.
For checking the speed, I downloaded "LAN speed test", and tried it out on a network share on one of the XP computers. For that one, reading/writing a 100MB test file, it measured out at writing 34.8 MBPS and and reading 24.8. When "slow", the NAS was reading/writing a 25MB file with speeds of 0.9 mbps writing and 0 reading (timed out).
When the NAS is unplugged and then powered on again, the write time is 23.5 mbps and 11.1 reading (25MB file again).
I will try resetting to factory defaults in the morning, and if that doesn't work, I'll seeing about returning it.
Thanks!
-
I haven't been a member here long but I haven't seen a problem like yours reported. Yea, seriously try to reset to factory defaults, reflash after obtaining a fresh downloaded copy fo the firmware just in case, although doubtful your last firmware was corrupt. I honestly don't see how it could be a drive issue but you never know. If you post the drive models then you would get feedback of if those specific models have been used by people.
-Joe
-
The drives are actually Seagate - both model ST35000320NS, 500G. 39 degrees Celsius, this morning.
Rebooted DNS 321, reset to factory settings, changed name, and ran LAN speed test - writing 22.7 mbps, reading 19.26 mbps.
5 minutes later, LAN Speed test reports 25.6 writing, 21.8 reading.
Will test again in an hour.
-
And it's back to being almost completely unresponsive - can see directory listing, but a speed test from various computers gets errors on reading/writing files.
Argh.
-
Sounds like the unit has a problem. I think I'd be looking for a box to ship it back. :)
-
I agree, looks like it's time to send it back.
If you do send it back and in the replacement NAS you have the same problem, try a different hard drive or just one at a time. Heck, you could try one at a time right now. I doubt it's your drives but stranger things have happened.
-
New DNS-321, same problem!
Argh. Makes me want to just throw in the towel and admit defeat.
-
Really sholland, it doesn't sound like it's your 321 causing your grief. I'm also wondering if it's a possible problem with 1 or both of your drives, although as Joe has said, that would be exceedingly odd but not impossible. A few things you could try here:
1. Try getting a file that is close to 100 megs and then move it around your home network, PC to PC, if it is set up so that each PC can see each other.
2. Are you using a switch or a router? Try rebooting your switch or router when the slowdown occurs.
I'd like to see you rule out the other common denominators between the NAS and each PC. Your switch or router would be almost the only other piece of hardware that I can currently think of (after a very long 12 hour shift at work!).
Ryder
-
I agree with Ryder that it could be one of your hard drives. I have seen hard drives start having bad reads after they run for a while but you can restart them and they work okay for a while. What happens is that every time the drive reads a sector it compares the CRC on the sector with the CRC it calculates on the read. If there is a problem it rereads the sector again. If after so many tries it cannot get a proper read the drive then times out with an error. If after several tries it gets a successful CRC compare it goes on. But since it has to reread every sector several times it just appears to run slow. If this is the case the drive will fail shortly.
I would probably pull one of the drives and reformat the remaining one. I cannot remember if it makes a difference which drive you pull but maybe one of the other guys can tell us. Then do your speed test again and see what happens. If you still have the trouble then swap drives and repeat. It should tell you if and which one is the problem. I am guessing that one of the drives will not make it through format. Also, if drive one fails then try drive two. If it also fails then it is probably the DNS-321. I have not seen two drives fail at the same time the same way.
I also agree with everyone else that I have not seen this before on the DNS-321. But this drive problem I have seen on desktops over the years and I am sure that it applies here.
Terry
-
OK - new fun tests and results.
I didn't test the hard drives, but I did check to see if the network was affecting it, by taking the NAS home and plugging it into my home network. And it worked just fine - faster speeds and no slow down even after 1 day.
So my guess is that it's something to do with the network, which I'm not that great at trouble-shooting. I did plug the NAS into the access point in my office (dlink DAP-1522), and it worked wonderfully for about an hour, at which point it slowed down dramatically again.
The truly weird thing is that I've also run speed tests on shared computer directories, and I'm not seeing any slowdown with file access to those directories - just a slowdown to the NAS.
Any suggestions for this? The router is a Dlink DIR-625, firmware up to date.
-
You seem to have narrowed it down to some sort of issue with the network at your workplace. Some things to try...
Replace the network cable. It might work fine with a PC, might look fine, but there's always a chance the cable could be flaky. Ask any IT folk and I'm sure they'll have a "doh!" story with an intermittent cable as the culprit.
There could be a virus/trojan/worm clogging up the network. This might result in DoS attacks that affect the DNS-321 more than PCs. The DNS-321 runs Linux and has different attacks/vulnerabilities than Windows. Scan every PC at work thoroughly, or alternatively take them all offline except for a known clean PC and see how the '321 performs. The most conclusive way to tell is to put a machine on the network that sniffs and analyzes packets, but that's beyond the scope of the average user.
-
sholland,
peas had some good suggestions there, I'd investigate those avenues as well.
And since this seems to be a truly odd problem, you may want to try this too.
Are you plugging your 321 into the same port on the router all the time? if so, try a different port, preferably away from the one you currently use. There may be an issue with just one port on it, that has happened to me too many times to want to remember!
Also, you reported that the temp was 39C, first thing in the morning I'm assuming? Was that the temp of the drives, or the enclosure? You might want to try monitoring the temps of the drives and the enclosure after running for awhile, and especially after it starts to slow down. Also check to see if you can feel or hear the fan come on blow. Excess heat buildup after running for awhile can cause things to slow down dramatically sometimes.
There, now you have several things to try out for us. Please keep us posted as you have been, I am very curious to know what will eventually sort this very odd situation out for you.
Ryder
-
Thanks for the ideas.
I did check the network cable already, so failing the same problem effecting different cables, it's not that.
I'm going to be checking network traffic now, and going through and thoroughly looking at the two older XP systems. They do have virus scanners (Microsoft Security Essentials now, previous Norton AntiVirus 2005), but not sure as to all the details as to how they were set up.
I did download WireShark, but unfortunately nothing leaps out at me as being the problem - not that I'm sure I'd be able to tell or not!
-
Sarah,
I have two things for you, the first is questions, the second something which should be easy to try...
You said you have three computers, does that mean just connected to the DAP-1522 or three computers total on your network (includes wireless connectivity). If you are using the wireless then another computer could be scanning, whatever to your NAS. Also, is the DAP-1522 connected to the internet? Right now I'm picturing three computers with ethernet cables feeding into the back of the DAP-1522 and one cable feeding to the NAS, all ports full. This means no ethernet to connect to the internet or any other outside system unless you are using wireless.
I'm curious if your DAP-1522 has QOS settings and you may need to adjust or disable.
Test:
One easy thing you could try is to replace the DAP-1522 with an ethernet switch or a different router (not the same model). See if the problem goes away. If you use a switch and the DAP-1522 was providing DHCP, then you would need to manually setup the IP addresses on each computer and possibly on the NAS depending on your setup. I just don't see the need to troubleshoot network traffic since you only have three computers.
-Joe
-
Joe,
I've been checking the DAP-1522 out, and not sure if it's a problem or not.
Firstly, though, the network situation. This is made more interesting by this being an older concrete building, and difficult to run cables into. The computer #1 (XP) is connected directly to the router. Computer #2 (XP) takes a more circuitous route - down to the basement, into the phone closet, through a DLink DSH-5 hub, and then up to the router (only 2 connections to that hub). Computer #3 is mine, Win7, and connected to the DAP-1522 which is in my office. That's connected wirelessly to the router, and then currently my desktop, network printer in my office, and NAS are connected to that. Oops, there is a computer #4 at times, a wireless laptop, but hardly ever used.
The 1522 has QOS settings, which are not enabled.
At this point, I'm thinking seriously of getting a concrete drill and chipping through some walls myself to run actual physical cable - at the moment, if I look at the wireless connections on the router, I'm getting 81 mbps on that device:
IP Address Mode Rate (Mbps) Signal (%)
192.168.0.50 802.11n (2.4GHz) 81 88
That's after going through numerous tips on the DAP-1522 forum to try and increase the speed of that device...
And the silly NAS still doesn't consistently work!
More DAP-1522 settings:
Wireless Radio : Enabled
Status : connected
Channel : 9
Security Type : WPA2- Personal / Auto
Wi-Fi Protected Setup : Enabled / Configured
Replacing the DAP-1522 with another switch or router wouldn't be that easy. At some point, I think I'll try to come in sometime after hours, and test to see what it's like with that shut down, and the NAS plugged into the router (which is where it was originally, plugged it in up here to help with my rebooting it).
-
Sarah:
I would take a hard look at your network configuration. You might consider replacing your hub in the phone closet with a Linksys Pro Series Switch. Cost is $65.00 and comes with a lifetime policy. You should actually buy two of these and hook the second one up to the Router and your office computers up to the switch. This would allow Gigabit speeds between the computers, if the computers have gigabit network interface that is. I would also look in to the cabling between the computers and the hub in the phone closet, ensure they are Cat5e or Cat6 and are less than 300ft in length each. Last, I would take one of those Linksys switches for a test drive and at the end of the day, connect it to you Windows 7 PC and NAS. This means no DAP-1522 or other device. Verify the NAS is working and go home. In the morning if the NAS is not slow then connect the DAP-1522 to the switch. This meants you have a PC, NAS, and DAP-1522 connected to the switch. There is nothing connected to the DAP-1522 except the switch. Test that out for the day. AS long as the Windows 7 computer is using the NAS I think all will be fine. If you use a remote computer (over the DAP-1522) and it becomes slow again, maybe it's the DAP-1522 or your wireless router.
If you can do this before knocking a hole in the wall, that's great but I've alway preferred hard wired connections whenever possible.
-Joe
-
I'm still working on this issue, in my copious spare time. ::)
Haven't been able to tackle any hardware changes, but I did install ZoneAlarm on both the XP computers on the LAN. If I set the firewall to prohibit them from accessing the LAN, then the DNS-321 happily keeps on working at a decent speed.
If, however, I configure ZoneAlarm to allow them network access, my DNS-321 plummets in speed.
I wrote a little VB program that copies a 25 meg file to a directory and then reports on the speed, and it will continue to do this for specified intervals (that way I can get some work done in the intervals). Here's a report from today:
12/21/2009 1:41:42 PM 11328 kb/s n:\transfer\test.avi
12/21/2009 1:43:42 PM 12081 kb/s n:\transfer\test.avi
12/21/2009 1:45:42 PM 11990 kb/s n:\transfer\test.avi
12/21/2009 1:47:42 PM 10880 kb/s n:\transfer\test.avi
turned off XP Machine zone alarm (allowed it to communicate with LAN)
12/21/2009 1:50:33 PM 12348 kb/s n:\transfer\test.avi
12/21/2009 1:53:49 PM 330 kb/s n:\transfer\test.avi
12/21/2009 1:55:11 PM 0 kb/s n:\transfer\test.avi
12/21/2009 1:58:03 PM 279 kb/s n:\transfer\test.avi
12/21/2009 2:00:53 PM 271 kb/s n:\transfer\test.avi
12/21/2009 2:02:49 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:04:10 PM 315 kb/s n:\transfer\test.avi
12/21/2009 2:07:12 PM 225 kb/s n:\transfer\test.avi
12/21/2009 2:08:23 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:08:31 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:10:36 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:12:39 PM 311 kb/s n:\transfer\test.avi
12/21/2009 2:15:10 PM 653 kb/s n:\transfer\test.avi
12/21/2009 2:17:21 PM 518 kb/s n:\transfer\test.avi
turned on zone alarm for XP machine again
12/21/2009 2:27:33 PM 445 kb/s n:\transfer\test.avi
12/21/2009 2:29:48 PM 355 kb/s n:\transfer\test.avi
12/21/2009 2:31:59 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:33:10 PM 754 kb/s n:\transfer\test.avi
12/21/2009 2:34:47 PM 0 kb/s n:\transfer\test.avi
12/21/2009 2:37:14 PM 662 kb/s n:\transfer\test.avi
reboot NAS
12/21/2009 2:47:50 PM 8555 kb/s n:\transfer\test.avi
12/21/2009 2:49:50 PM 9280 kb/s n:\transfer\test.avi
12/21/2009 2:51:50 PM 9438 kb/s n:\transfer\test.avi
This happens for BOTH the XP machines! I've run numerous virus and mal-ware checkers on both machines, but I can't seem to WHY turning these on would affect anything.
Is there any way I can monitor what's hitting the DNS-321? Any other suggestions (short of rebuilding both machines?)
-
I don't know what else I could suggest but I wouldn't rebuild you machines, I doubt that would do anything.
-
Out of curiosity, what is the transfer speed between the machines?
-
Out of curiosity, what is the transfer speed between the machines?
I had wondered the same thing GRJ, back when I thought this was a home network. And now that I know it's not, I still wonder. I'd like to see how the machines themselves do when you move a set file or group of files back and forth between PCs. And if you find one that seems a bit suspicious, then move those same files around continuously between them 8-10 times. A nice mix of files would be good too, say a total of gig, but make one a 500 meg file, then 4x100 meg files and then 4x25 meg files. That should give everything involved a good bit of exercise and also show any problems, if there are any, with either small or large files too.
This problem is just so....weird! but, for every problem there is a solution, it's just a matter of finding it before ya strap 200 lbs of C-$ to the building to create those "holes in the wall" you had mentioned earlier sholland. ;) ;) :D
-
I've made some progress!
I went to both XP machines, and did two things - one was to remove this network key:
Disable Network Task Scheduler
(LAN Browsing Speedup)
This tweak disables searching networked computers for scheduled tasks. It reduces the long wait when opening network folders. To apply this tweak, find the following key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\RemoteComputer\NameSpace\
and delete this key:
{D6277990-4C6A-11CF-8D87-00AA0060F5BF}
I also removed the microsoft network, file and print sharing, and QOS from each machine's LAN setup, rebooted, and then added it back (with the exception of QOS). Oh, and one machine was accessing the network half duplex, but both were 100 (I've now set them to connect full instead of auto).
And it worked! And worked for all the afternoon. I even uninstalled ZoneAlarm from one of the computers, instead of just diable it, and it still worked for hours. My NAS access time was about 12000 kb/s, consistently, and both XP machines could access the NAS.
I'm out of the office right now, but left my machine on, and the NAS. If I'd been thinking, I'd have left my file speed checker going for the NAS all night. I just logged in remotely, and now I can't access the NAS - I can ping it, but it seems to be the painfully slow issue again. I can see that the XP machines were turned on about an hour ago.
So I don't know - does this mean that the XP machines are causing problems again? Is it just an overnight problem? If I could reboot the NAS, would it work during the day? I can't remotely reboot the NAS, at this point, to check - hmm, maybe I'll email the receptionist and have her unplug it and plug it back in.
Transfer speed is nothing to write home about, and something else I need to address, but they can all access each other peer to peer without being painfully slow. I'd have to get the speeds.
One thing - while it isn't a home network, it's not a high-end work network, if you get my meaning. ;)
-
So I don't know - does this mean that the XP machines are causing problems again? Is it just an overnight problem? If I could reboot the NAS, would it work during the day? I can't remotely reboot the NAS, at this point, to check - hmm, maybe I'll email the receptionist and have her unplug it and plug it back in.
Transfer speed is nothing to write home about, and something else I need to address, but they can all access each other peer to peer without being painfully slow. I'd have to get the speeds.
One thing - while it isn't a home network, it's not a high-end work network, if you get my meaning. ;)
I would venture to say that at this point, you would be the only one that could answer that question sholland. I'll listen for a scream or the lack of one to get my answer from you! ;) ;)
And yep, I get your meaning. But some homes have a far more complicated network than some businesses, so I guess it depends on yer definition of "high-end". My company is thinking of replacing it's high-end" email server and their "high-end" virus scanner, they are both 386 rigs right now, get my meaning? ;) ;)
Glad yer making progress though sholland, that should make you feel good at least. A nice way to cap off a nasty year I'd say! :D
-
Sarah,
When you get back to your machines I think you should take a look at those computers again, verify something didn't change back to original.
Did you ever try a network switch? Maybe you could buy or borrow one, try it out, if it works, keep it, if not, return it. I just bought a "Trendnet 5-port Gigabit GREENnet Switch - 5 x 10/100/1000Mbps Auto-MDIX RJ-45 Ports, IEEE 802.3x Flow Control" for $40.00. There are cheaper ones but I'd like to keep mine running for 5 years or more.
Did you ever hook the NAS up to the network switch in the closet?
-Joe
-
The correct workaround here is to install funplug and sshd. Once you have access to the device using Putty, run "top" which will tell you what is going on. The unit has a rudimentary Linux kernel but very limited memory. In addition, it does not handle multiple access very good and it's media server is not UPNP certified (and does not work in Windows7, I have confirmed this with Microsofts UPNP development team).
Since the unit has only a small amount of memory, most is used for the Linux kernel and only a little is left for OS disk cache. This will always end up blowing performance.
I ended up disabling the UPNP server on the DNS-321 configuration page. This caused the CPU to go from 100% in use performing an endless loop recaching of the media content to almost 0% CPU utilization during idle states (aka when top was not running ;)).
This opened up all the CPU for file transfers. QED, problem on file transfer speed corrected.
TheWitness
-
Aha! I *knew* there must be a way to figure out what was going on with the DNS-321 while it was running, but I'm not very linux-literate.
Here's several screen captures from TOP (not showing all items, just the top ones), and ranging from just recently restarted to seized up:
/ # top
Mem: 59396K used, 2432K free, 0K shrd, 19796K buff, 20436K cached
CPU: 0% usr 69% sys 0% nice 0% idle 0% io 0% irq 30% softirq
Load average: 2.39 2.04 1.06
PID PPID USER STAT VSZ %MEM %CPU COMMAND
872 2 root DW< 0 0% 53% [md0_resync]
865 2 root SW< 0 0% 35% [md0_raid1]
2152 2151 root R 1356 2% 12% top
1637 1 root S 8364 13% 0% /web/webs
1877 1375 root S 6012 10% 0% smbd -D
1375 1 root S 5740 9% 0% smbd -D
1380 1375 root S 5740 9% 0% smbd -D
1753 1 root S 4016 6% 0% pure-ftpd (SERVER)
Mem: 59228K used, 2600K free, 0K shrd, 18668K buff, 22472K cached
CPU: 0% usr 99% sys 0% nice 0% idle 0% io 0% irq 0% softirq
Load average: 15.42 13.70 8.
PID PPID USER STAT VSZ %MEM %CPU COMMAND
2390 1375 nobody R 6012 10% 72% smbd -D
2403 1375 nobody R 6012 10% 26% smbd -D
2440 1375 nobody R 6024 10% 0% smbd -D
2152 2151 root R 1360 2% 0% top
872 2 root DW< 0 0% 0% [md0_resync]
865 2 root SW< 0 0% 0% [md0_raid1]
Mem: 60064K used, 1764K free, 0K shrd, 18672K buff, 23296K cached
CPU: 0% usr 100% sys 0% nice 0% idle 0% io 0% irq 0% softirq
Load average: 15.07 13.68 8.
PID PPID USER STAT VSZ %MEM %CPU COMMAND
2424 1375 nobody R 6012 10% 100% smbd -D
2152 2151 root R 1360 2% 0% top
55 2 root DW< 0 0% 0% [kswapd0]
1637 1 root S 8364 13% 0% /web/webs
2440 1375 nobody R 6024 10% 0% smbd -D
1877 1375 nobody R 6012 10% 0% smbd -D
2390 1375 nobody R 6012 10% 0% smbd -D
2403 1375 nobody R 6012 10% 0% smbd -D
2350 1375 nobody D 6012 10% 0% smbd -D
1375 1 root S 5740 9% 0% smbd -D
1380 1375 root S 5740 9% 0% smbd -D
1753 1 root S 4016 6% 0% pure-ftpd (SERVER)
Mem: 60600K used, 1228K free, 0K shrd, 18644K buff, 23836K cached
CPU: 0% usr 99% sys 0% nice 0% idle 0% io 0% irq 0% softirq
Load average: 13.86 13.64 9.
PID PPID USER STAT VSZ %MEM %CPU COMMAND
1877 1375 nobody R 6012 10% 77% smbd -D
2403 1375 nobody R 6012 10% 22% smbd -D
2152 2151 root R 1360 2% 0% top
2440 1375 nobody R 6024 10% 0% smbd -D
1637 1 root S 8364 13% 0% /web/webs
2390 1375 nobody R 6012 10% 0% smbd -D
2424 1375 nobody R 6012 10% 0% smbd -D
2350 1375 nobody D 6012 10% 0% smbd -D
1375 1 root S 5740 9% 0% smbd -D
1380 1375 root S 5740 9% 0% smbd -D
1753 1 root S 4016 6% 0% pure-ftpd (SERVER)
Mean anything to anyone? ???
-
The "resync" tells me that something was/is being written to the partition and it's performing a software raid (unfortunate), or that the disks are out of sync, like you had a soft error and the disks had to resync. The "smbd" are actual file transfers. As you can see, one smbd is able to eat the entire CPU, which means that as every subsequent consumer comes on board, the throughput is going to drop.
TheWitness
-
I am surprised at the number of smbds on there - the only thing that ought to have been transferring files was one program on one machine.
Whyintheheck was one smbd eating the whole CPU? And more importantly, how can I prevent it?
-
By default, there are two smbd's running as the root process. Then, for every connection to the file system (someone doing something), there will be another smpd "forked" running as the connected user. If you want to see who is connected, you can run the following command (I hope anyway).
netstat
That will show all the IP address of people connected to the box.
TheWitness
-
Actually, I have four of them running with no access currently going on.
Mem: 59868K used, 1944K free, 0K shrd, 14800K buff, 29008K cached
CPU: 0% usr 0% sys 0% nice 99% idle 0% io 0% irq 0% softirq
Load average: 0.00 0.00 0.02
PID PPID USER STAT VSZ %MEM %CPU COMMAND
3083 3082 root R 1360 2% 0% top
1607 1 root S 6656 11% 0% /web/webs
2309 2302 root S 5140 8% 0% /usr/sbin/samba/smbd -D
2302 1 root S 4836 8% 0% /usr/sbin/samba/smbd -D
2308 2302 root S 4836 8% 0% /usr/sbin/samba/smbd -D
2306 1 root S 2968 5% 0% /usr/sbin/samba/nmbd -D
1788 1 root S 2964 5% 0% pure-ftpd (SERVER)
1753 1 root S 1600 3% 0% crond
1 0 root S 1596 3% 0% init
-
everything is idle at the moment. So, no one is accessing anything. You are going to see them running. Again, if you run netstat or netstat -a you will see active and idled connections. When the last connection is fully down, I imagine one or more "smbd" will exit.
TheWitness
-
While this info looks interesting, the only thing I can take from this is what programs were running and eating up CPU time. Is there any way to tell the actual user (computer) performing the file transfer? Maybe there is one of the three causing an issue with some kind of scanning of the NAS?
-
Well, there are a couple of machines sleeping that keep their My Documents folders over there, that's probably a couple of them. :)
-
There is a "feature", if you want to call it that, in Windows, where Explorer will scan all files in a directory for their file type and attempt to show an appropriate "preview" of the file. This was a "nasty" feature, especially for a large organization with thousands of users hitting the shares a the same time. I don't know how to turn down the "preview" mode. You might want to investigate that. It's been too long for me now. I know that it can be adjusted from the registery, but I don't know about explorer.
TheWitness