![]() > from hfs under Linux is CPU intense: You can find out by trying it on That could be an issue, when writing to a USB disk. > On the rpi if I'm not mistaken the eth port is also connected over the > network connection in the middle of a backup. Another problem is data corruption, if you cut the > is slow to backup especially the first time it takes very long. > (we have 100% eco power here, but yes, don't tell me.). > probably in the same class than a rpi4 CPU and the load is really low > I backup since years to an Opteron 1212 driven machine, which is > mke2fs -b 4096 -E -j -L timemachine -m1 -O dir_index,extent,filetype, > formatting with ext4 use something like > As others have said, use a well supported file system on the rpi. > HUGE throughput improvements over prior hardware. > Also, the Pi 4 fixes the shared bus issue. > I believed that Time Machine had a hard requirement for hfs. Josh / computer once beat me at chess, but it was no match for me at kickboxing. It just has to be a filesystem that the host server likes. The underlying filesystem on the server's disk doesn't matter, as long as it can handle large enough files (so.not FAT16). But since you're backing up to a network volume, it'll make a Sparse Disk Image bundle to handle that, and back up to the HFS+ volume contained on that disk image. The file system that Time Machine backs up to will need to be HFS+. > never ever, nobody would do that and for the cient it#s not even visible ![]() > It may be a bad idea - but "nobody ever?" - I actually made a sincere effort to make that work. > On May 28, 2020, at 9:25 AM, Tom Cooper wrote: Speak your mind and fear less the label of "crackpot" than the stigma of conformity." Expose your ideas to the danger of controversy. Telegram: the path of the unsafe, independent thinker. I actually ran with this configuration for a while, I figured if I needed to recover my backups using a mac, it’d helpful to have it on HFS+ - it does work fine, and HFS+ support in linux is pretty good. ![]()
0 Comments
Leave a Reply. |