看板 DFBSD_bugs 關於我們 聯絡資訊
Joel K. Pettersson <joelkpettersson@gmail.com> added the comment: I just thought of (in hindsight obvious) logging into single-user mode to g= et a full output in one place; however, trying then to reproduce it the hammer e= rrors were the end of the issue. The second error message was merely the "Forcing read-only mode" one. I noticed doing multiple attempts that the inode numbered in the first mess= age was the same (4295132199), and I wondered if the problem could be due to filesystem corruption as a result of writing after the triggering (but, I suppose, before detection) of the now-fixed first problem - and so I tried reformatting the USB-connected drive, and then it - and further data copyin= g - worked. So I suppose the problem is resolved. ---------- status: chatting -> resolved _____________________________________________________ DragonFly issue tracker <bugs@lists.dragonflybsd.org> <http://bugs.dragonflybsd.org/issue1418> _____________________________________________________