https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243421
Bug ID: 243421
Summary: Zfs send/recv backup over USB 3.0/eSATA crashes /dev
after 466 GB
Product: Base System
Version: 12.1-RELEASE
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: b...@freebsd.org
Reporter: j...@xyinn.org
Hello all,
I made a post earlier in the week on the FreeBSD forums in extensive detail to
see if I could get a solution before having to file a bug report
(https://forums.freebsd.org/threads/dev-directory-basically-acompletely-empty-after-4-8-hours-after-i-start-an-external-drive-over-usb-backup-zfs-send-recv.73699/).
Since after doing various tests and purchasing new equipment (with FreeBSD
compatible parts), it still didn't solve the issue.
TLDR: For whatever reason when I do a zfs send | recv from my OS pool (tank) to
my backup pool (backup) over USB 3.0 or eSATA, once the stream hits 466 GB (469
GB in this particular dataset, and a few hundred for GB in other datasets), the
zfs program crashes, and the entire /dev directory vanishes. The only thing
left in /dev after this is "null". This effectively means that even though
FreeBSD is still running, most applications stop functioning since they can't
find any resources in /dev (Example: zpool status would no longer work since it
can't communicate with the hardware via /dev/zfs). It's very weird since I
don't see any error messages in 'dmesg'. It's like it's a "clean crash".
At the moment I will leave FreeBSD running on the box to see if we can resolve
this, but if not I will need to switch back to Linux since this is literally
preventing me from making my external pool backups.
Thank you and please let me know if there is any other info I can provide.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-bugs@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscr...@freebsd.org"
