November 4, 201312 yr My syslog shows the following error over and over again: Whats up with this? My large back up of photos seems to be progressing. (300gigs Attached is a screen shot of the control panel. Thanks for any help! Nov 4 13:52:22 Tower kernel: mvsas 0000:01:00.0: Phy0 : No sig fis Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2006:phy0 Attached Device Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x89800. Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x1001 Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2088:port 0 attr is 0 Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2114:phy0 Unplug Notice Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x199800. Nov 4 13:52:22 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x81 Nov 4 13:52:22 Tower shfs: shfs_write: write: (28) No space left on device Nov 4 13:52:32 Tower last message repeated 83 times Nov 4 13:52:32 Tower kernel: mvsas 0000:01:00.0: Phy0 : No sig fis Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2006:phy0 Attached Device Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x99800. Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x1001 Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2088:port 0 attr is 0 Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2114:phy0 Unplug Notice Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x199800. Nov 4 13:52:32 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x81 Nov 4 13:52:32 Tower shfs: shfs_write: write: (28) No space left on device Nov 4 13:52:42 Tower last message repeated 81 times Nov 4 13:52:42 Tower kernel: mvsas 0000:01:00.0: Phy0 : No sig fis Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2006:phy0 Attached Device Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x99800. Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x1001 Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2088:port 0 attr is 0 Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2114:phy0 Unplug Notice Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2069:port 0 ctrl sts=0x199800. Nov 4 13:52:42 Tower kernel: /usr/src/sas/trunk/mvsas_tgt/mv_sas.c 2071:Port 0 irq sts = 0x81 Nov 4 13:52:42 Tower shfs: shfs_write: write: (28) No space left on device
November 4, 201312 yr You have 1 drive with no space left on it. Either split level or drive inclusion/exclusion on shares is probably the cause. Sent from a mobile device, sorry for any typos.
November 5, 201312 yr You have 1 drive with no space left on it. Either split level or drive inclusion/exclusion on shares is probably the cause. Sent from a mobile device, sorry for any typos. or you do not have the min-free-space parameter defined for that share.
Archived
This topic is now archived and is closed to further replies.