NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Hernexto
Oct 26, 2017Star
ReadyNAS 6 stops working: kernel: fd_do_rw() write returned -28
Hi!
After 2 months, with LogAnalyzer's filesystem corruption and this error I'm still unable to use the unit.
I will write it here in case somebody has the same problem and I will open a ticket if needed.
This is happening ever few days at night, around 2 AM something happens and journald log gets full with:
kernel: fd_do_rw() write returned -28
Even configuring journald to take up to 2 GB, it happens from 5 to 20 times per second.
Sometimes it also appears this similar one:
kernel: FILEIO: fallocate() failed: -28
At night, from 20h to 8h all backups are done, ntbackup via Samba share and VEEAM via iSCSI LUN . VEEAM shows this error on all backups after problem appears:
Error: Client error: Device is not ready. Error code: 21 Failed to flush file buffers.
File: [F:\Backups\Backup SRVCORREO\Backup SRVCORREO2017-10-25T030031.vbk].
Samba works, it's only the LUN. Rebooting Win2012+VEEAM does nothing you must reboot ReadyNAS.
LOG: (nothing earlier looks to be useful anyway)
-- Logs begin at Wed 2017-10-25 09:58:23 CEST, end at Thu 2017-10-26 15:30:13 CEST. --
Oct 26 00:01:15 NASNG dbus[3351]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Oct 26 00:01:16 NASNG dbus[3351]: [system] Successfully activated service 'org.opensuse.Snapper'
Oct 26 00:05:01 NASNG CRON[16246]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 00:05:01 NASNG CRON[16250]: (root) CMD (/frontview/bin/fvbackup 001 &> /dev/null)
Oct 26 00:05:01 NASNG CRON[16246]: pam_unix(cron:session): session closed for user root
Oct 26 00:05:01 NASNG fvbackup-q[3967]: Command: enqueue:1
Oct 26 00:05:01 NASNG fvbackup-q[3967]: write(/var/log/frontview/backup/status_backup_001,BACKUP_STATUS__IN_QUEUE!!1508969101!!OK)
Oct 26 00:05:01 NASNG fvbackup-q[3967]: Push: job_id=1 q_wp=0 q_rp=0
Oct 26 00:05:05 NASNG fvbackup-q[3967]: cmd=/frontview/bin/fvbackup -e 1
Oct 26 00:05:09 NASNG fvbackup-q[3967]: Create a readonly snapshot of '/data/Backup' in '/data/._share/Backup/.snapshot/b_1508969106_16256'
Oct 26 00:09:01 NASNG CRON[16288]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 00:09:01 NASNG CRON[16292]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 26 00:09:01 NASNG CRON[16288]: pam_unix(cron:session): session closed for user root
Oct 26 00:13:48 NASNG connmand[3358]: ntp: adjust (slew): -0.006185 sec
Oct 26 00:14:55 NASNG sshd[16380]: SSH: Server;Ltype: Version;Remote: 192.168.5.152-65226;Protocol: 2.0;Client: PuTTY_Release_0.70
Oct 26 00:14:55 NASNG sshd[16380]: SSH: Server;Ltype: Kex;Remote: 192.168.5.152-65226;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none [preauth]
Oct 26 00:14:55 NASNG sshd[16380]: SSH: Server;Ltype: Authname;Remote: 192.168.5.152-65226;Name: root [preauth]
Oct 26 00:15:02 NASNG sshd[16380]: pam_winbind(sshd:auth): getting password (0x00000000)
Oct 26 00:15:02 NASNG sshd[16380]: pam_winbind(sshd:auth): request wbcLogonUser failed: WBC_ERR_AUTH_ERROR, PAM error: PAM_USER_UNKNOWN (10), NTSTATUS: NT_STATUS_NO_SUCH_USER, Error message was: No such user
Oct 26 00:15:02 NASNG sshd[16380]: pam_winbind(sshd:account): valid_user: wbcGetpwnam gave WBC_ERR_DOMAIN_NOT_FOUND
Oct 26 00:15:02 NASNG sshd[16380]: Accepted password for root from 192.168.5.152 port 65226 ssh2
Oct 26 00:15:02 NASNG sshd[16380]: pam_unix(sshd:session): session opened for user root by (uid=0)
Oct 26 00:15:02 NASNG sshd[16380]: SSH: Server;Ltype: Kex;Remote: 192.168.5.152-65226;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
Oct 26 00:17:01 NASNG CRON[16415]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 00:17:01 NASNG CRON[16419]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 26 00:17:01 NASNG CRON[16415]: pam_unix(cron:session): session closed for user root
Oct 26 00:30:52 NASNG connmand[3358]: ntp: adjust (slew): -0.008077 sec
Oct 26 00:31:40 NASNG sshd[9802]: SSH: Server;Ltype: Kex;Remote: 192.168.5.121-61543;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
Oct 26 00:39:01 NASNG CRON[16585]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 00:39:01 NASNG CRON[16589]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 26 00:39:02 NASNG CRON[16585]: pam_unix(cron:session): session closed for user root
Oct 26 00:47:56 NASNG connmand[3358]: ntp: adjust (slew): +0.029760 sec
Oct 26 01:01:17 NASNG dbus[3351]: [system] Activating service name='org.opensuse.Snapper' (using servicehelper)
Oct 26 01:01:17 NASNG dbus[3351]: [system] Successfully activated service 'org.opensuse.Snapper'
Oct 26 01:05:00 NASNG connmand[3358]: ntp: adjust (slew): -0.037031 sec
Oct 26 01:09:01 NASNG CRON[17143]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 01:09:01 NASNG CRON[17147]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 26 01:09:01 NASNG CRON[17143]: pam_unix(cron:session): session closed for user root
Oct 26 01:15:02 NASNG sshd[16380]: SSH: Server;Ltype: Kex;Remote: 192.168.5.152-65226;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
Oct 26 01:17:01 NASNG CRON[17253]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 01:17:01 NASNG CRON[17257]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Oct 26 01:17:01 NASNG CRON[17253]: pam_unix(cron:session): session closed for user root
Oct 26 01:22:04 NASNG connmand[3358]: ntp: adjust (slew): +0.003810 sec
Oct 26 01:31:40 NASNG sshd[9802]: SSH: Server;Ltype: Kex;Remote: 192.168.5.121-61543;Enc: aes256-ctr;MAC: hmac-sha2-256;Comp: none
Oct 26 01:39:01 NASNG CRON[17426]: pam_unix(cron:session): session opened for user root by (uid=0)
Oct 26 01:39:01 NASNG CRON[17430]: (root) CMD ( [ -x /usr/lib/php5/sessionclean ] && /usr/lib/php5/sessionclean)
Oct 26 01:39:01 NASNG CRON[17426]: pam_unix(cron:session): session closed for user root
Oct 26 01:39:08 NASNG connmand[3358]: ntp: adjust (slew): -0.001889 sec
Oct 26 01:56:12 NASNG connmand[3358]: ntp: adjust (slew): +0.007998 sec
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Oct 26 02:00:39 NASNG kernel: fd_do_rw() write returned -28
Any clue? Any help to find the problem?
1 Reply
Replies have been turned off for this discussion
Error -28 is no space left on device, but it is wrong:
LUN has 500 GB (of 3 TB) still free (chkdsk passed) and ReadyNAS:
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 803M 2.9G 22% /
tmpfs 979M 0 979M 0% /dev/shm
tmpfs 979M 3.6M 975M 1% /run
tmpfs 490M 4.6M 485M 1% /run/lock
tmpfs 979M 0 979M 0% /sys/fs/cgroup
/dev/md127 5.5T 3.7T 1.8T 67% /data
/dev/md127 5.5T 3.7T 1.8T 67% /apps
/dev/md127 5.5T 3.7T 1.8T 67% /homeCould it be related to some BTRFS bug or reserved blocks?
http://logs.tvrrug.org.uk/logs/%23btrfs/2016-04-11.html#2016-04-11T07:25:23
root@NASNG:~# btrfs fi usage -T /data
Overall:
Device size: 5.44TiB
Device allocated: 4.49TiB
Device unallocated: 980.15GiB
Device missing: 0.00B
Used: 3.66TiB
Free (estimated): 1.78TiB (min: 1.30TiB)
Data ratio: 1.00
Metadata ratio: 2.00
Global reserve: 512.00MiB (used: 0.00B)
Data Metadata System
Id Path single DUP DUP Unallocated
-- ---------- ------- -------- --------- -----------
1 /dev/md127 4.47TiB 13.00GiB 16.00MiB 980.15GiB
-- ---------- ------- -------- --------- -----------
Total 4.47TiB 6.50GiB 8.00MiB 980.15GiB
Used 3.65TiB 4.80GiB 608.00KiBLUN size is 3.5Tb, 2.5Tb are currently used and probably 2.9Tb was the maximum used.
root@NASNG:/# ls -lh /data/veeambackups/.iscsi
total 2.9T
-rwxrwxrwx 1 guest guest 3.5T Oct 26 19:09 iscsi_lun_backing_store
root@NASNG:/# du -sh /data/*
799G /data/Backup
2.8G /data/Drivers
0 /data/home
304G /data/ImagenDisco
0 /data/Pirovano
8.1M /data/rsyslog
25G /data/Software
2.9T /data/veeambackupsI copied 400 Gb (from 2.5 to 2.9Tb) and no problems so THERE IS free space.
any clue?
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!