Follow this how to: http://jonarcher.info/2015/02/getting-fedora-21-raspberry-pi-2/ I have load and update a official F21 arm7 (minimal install) on a new raspberry PI 2, to make network backup of some server on a 1Gb USB hd via rsync. > Linux s-backup-lampo 3.18.12-v7+ #783 SMP PREEMPT Tue May 5 22:48:52 BST 2015 armv7l armv7l armv7l GNU/Linux Apparent all work find, but after a while rsync run, the mount point go in read only mode and rsync stop to work with this error: > rsync: write failed on "/mnt/metal-bk-1t/temp2/dir/file": Input/output error (5) > rsync error: error in file IO (code 11) at receiver.c(393) [receiver=3.1.1] And in dmesg and journalctl I see a lot of this message: > mag 11 09:01:17 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned. > .... If I try unmount the device, the umount command still blocked and into journalctl I see this error: > mag 11 09:57:26 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned. > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: INFO: task umount:812 blocked for more than 120 seconds. > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: Not tainted 3.18.12-v7+ #783 > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: umount D 80521780 0 812 678 0x00000001 > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<80521780>] (__schedule) from [<80521c70>] (schedule+0x40/0x8c) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<80521c70>] (schedule) from [<7f259530>] (xfs_ail_push_all_sync+0xb8/0xf8 [xfs]) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<7f259530>] (xfs_ail_push_all_sync [xfs]) from [<7f2436e4>] (xfs_unmountfs+0x58/0x194 [xfs] > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<7f2436e4>] (xfs_unmountfs [xfs]) from [<7f24530c>] (xfs_fs_put_super+0x28/0x5c [xfs]) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<7f24530c>] (xfs_fs_put_super [xfs]) from [<8013ed4c>] (generic_shutdown_super+0x80/0xe8) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<8013ed4c>] (generic_shutdown_super) from [<8013f0a0>] (kill_block_super+0x28/0x78) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<8013f0a0>] (kill_block_super) from [<8013f400>] (deactivate_locked_super+0x6c/0x80) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<8013f400>] (deactivate_locked_super) from [<8013fa00>] (deactivate_super+0x68/0x6c) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<8013fa00>] (deactivate_super) from [<8015a900>] (cleanup_mnt+0x4c/0x88) > mag 11 09:57:31 s-backup-lampo.ansaldisrl.it kernel: [<8015a900>] (cleanup_mnt) from [<8015a9b8>] (__cleanup_mnt+0x1c/0x20) > mag 11 09:57:32 s-backup-lampo.ansaldisrl.it kernel: [<8015a9b8>] (__cleanup_mnt) from [<8003e6c8>] (task_work_run+0xc0/0xf0) > mag 11 09:57:32 s-backup-lampo.ansaldisrl.it kernel: [<8003e6c8>] (task_work_run) from [<80012804>] (do_work_pending+0xd8/0xdc) > mag 11 09:57:32 s-backup-lampo.ansaldisrl.it kernel: [<80012804>] (do_work_pending) from [<8000eb18>] (work_pending+0xc/0x20) > mag 11 09:57:43 s-backup-lampo.ansaldisrl.it sudo[835]: lesca : TTY=pts/2 ; PWD=/home/lesca ; USER=root ; COMMAND=/bin/bash > mag 11 09:57:43 s-backup-lampo.ansaldisrl.it sudo[835]: pam_unix(sudo-i:session): session opened for user root by lesca(uid=0) > mag 11 09:57:56 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned. > mag 11 09:58:26 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned. > mag 11 09:58:56 s-backup-lampo.ansaldisrl.it kernel: XFS (sda1): xfs_log_force: error -5 returned. the only solution for get control of USB hd is restart the raspberry I have test the USB disk on another PC whit fedora 21 with same kind backup and work great Someone have some suggest? Many thanks for your help. -- Dario Lesca (inviato dal mio Linux Fedora 21 con Gnome 3.14) -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
