Jump to content

Serious usability / performance issues on 6b12 server

jrhamilt

By jrhamilt
in General Support

Recommended Posts

jrhamilt Apprentice

jrhamilt

Posted
Posted

So,  I've been using 6b12 for quite a while now, and just recently (like, after I upgraded the GUI to the 2015-01-21 version last week), the server has been severely stalling out.

 

Suddenly, when accessing the drives from Windows, I can't navigate file structures without a 20-30 second pause between actions.  Even some of the screens on the UI don't seem to want to perform at speed.

 

From the console, "top" doesn't seem to indicate excessive processor or memory consumption.

 

Something strange is going on.  A reboot of the server (after shutting down the array) seems to help a lot.  For the attached syslog, I was subsequently able to perform a graceful shutdown.  The previous time this occurred, I couldn't get the array stopped, and had to physically restart the server (hold button for 5 seconds).

 

Any thoughts?

syslog.txt

Link to comment
pkn Enthusiast

pkn

Posted
Posted
...

 

Suddenly, when accessing the drives from Windows, I can't navigate file structures without a 20-30 second pause between actions.  ...

If it's Windoze 7 or 8, check this out, it helped me with similar (although local to my laptop) problem:

 

http://www.istartedsomething.com/20121202/quick-fix-for-very-slow-to-load-downloads-folder-in-windows-7-8/

 

Another thought that it might be that the disk your are accessing was sleeping and needs time to spin up.

Link to comment
jrhamilt Apprentice

jrhamilt

Posted
  • Author
Posted

Isn't a spin up/down issue, as reads are slow for 20 minutes or more (until I reset). Once it gets slow, rebooting the server fixes it.

 

After the reboot, the drive is fine, which makes me think that it's not a Windows issue.

 

Hoping someone can check the syslog and find something there...

Link to comment
jonp Mentor

jonp

Posted
Posted

Looking at the log, looks like read errors over CIFS. Anyone else ever seen these before?

 

07:46:33 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:46:33 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:46:39 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:46:39 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:48:57 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:48:57 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:56:56 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:56:56 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:57:03 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:57:03 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 08:08:06 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 08:08:06 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 09:14:01 WhiteNAS kernel: mdcmd (41): spindown 2 Feb 9 09:41:20 WhiteNAS kernel: mdcmd (42): spindown 1 Feb 9 11:49:51 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:49:51 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 11:49:51 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:49:51 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 11:50:02 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:50:02 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:12 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:12 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:13 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:13 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:23 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:23 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:50:29 WhiteNAS kernel: mdcmd (43): spindown 2 Feb 9 13:42:03 WhiteNAS kernel: mdcmd (44): spindown 1 Feb 9 14:49:47 WhiteNAS kernel: mdcmd (45): spindown 1 Feb 9 15:50:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 15:50:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 15:50:40 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:40 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:14 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:14 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:15 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:15 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:25 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:25 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:51:04 WhiteNAS kernel: mdcmd (46): spindown 2 Feb 9 18:03:04 WhiteNAS kernel: mdcmd (47): spindown 1 Feb 9 18:03:05 WhiteNAS kernel: mdcmd (48): spindown 2 Feb 9 19:51:07 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:07 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 19:51:07 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:07 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 19:51:18 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:18 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:12:02 WhiteNAS rpc.mountd[2773]: authenticated mount request from 192.168.1.63:927 for /mnt/user/Media (/mnt/user/Media) Feb 9 20:15:19 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:19 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:15:19 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:19 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:15:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13

Link to comment
jrhamilt Apprentice

jrhamilt

Posted
  • Author
Posted

Looking at the log, looks like read errors over CIFS. Anyone else ever seen these before?

 

07:46:33 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:46:33 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:46:39 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:46:39 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:48:57 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:48:57 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:56:56 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:56:56 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 07:57:03 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 07:57:03 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 08:08:06 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 08:08:06 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 09:14:01 WhiteNAS kernel: mdcmd (41): spindown 2 Feb 9 09:41:20 WhiteNAS kernel: mdcmd (42): spindown 1 Feb 9 11:49:51 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:49:51 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 11:49:51 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:49:51 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 11:50:02 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 11:50:02 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:12 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:12 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:13 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:13 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:13:23 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 12:13:23 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 12:50:29 WhiteNAS kernel: mdcmd (43): spindown 2 Feb 9 13:42:03 WhiteNAS kernel: mdcmd (44): spindown 1 Feb 9 14:49:47 WhiteNAS kernel: mdcmd (45): spindown 1 Feb 9 15:50:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 15:50:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 15:50:40 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 15:50:40 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:14 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:14 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:15 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:15 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:14:25 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 16:14:25 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 16:51:04 WhiteNAS kernel: mdcmd (46): spindown 2 Feb 9 18:03:04 WhiteNAS kernel: mdcmd (47): spindown 1 Feb 9 18:03:05 WhiteNAS kernel: mdcmd (48): spindown 2 Feb 9 19:51:07 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:07 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 19:51:07 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:07 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 19:51:18 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 19:51:18 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:12:02 WhiteNAS rpc.mountd[2773]: authenticated mount request from 192.168.1.63:927 for /mnt/user/Media (/mnt/user/Media) Feb 9 20:15:19 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:19 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:15:19 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:19 WhiteNAS kernel: CIFS VFS: Send error in read = -13 Feb 9 20:15:29 WhiteNAS kernel: Status code returned 0xc0000054 NT_STATUS_FILE_LOCK_CONFLICT Feb 9 20:15:29 WhiteNAS kernel: CIFS VFS: Send error in read = -13

 

I *believe* I only see that when it's running the Crashplan Docker...  I'll see if I can't confirm that, but I don't remember seeing it before I started playing with Docker.

Link to comment

Archived

This topic is now archived and is closed to further replies.

Go to topic listing
×
×
  • Create New...