• 1 Post
  • 27 Comments
Joined 9 months ago
cake
Cake day: December 17th, 2023

help-circle

  • Pretty much when you posted that, I found this in my dmesg:

    [  715.744332] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
    [  715.965683] e1000e 0000:00:1f.6: The NVM Checksum Is Not Valid
    [  716.008541] e1000e: probe of 0000:00:1f.6 failed with error -5
    

    Just for the record, I compared modinfo up against lspci, and the PCI ID matches, so the driver should work. Is it possible to ignore the NVM checksum and try anyway? Because any tool I can find that communicates with the EEPROM on a hardware level is made for msdos.









  • I don’t remember how many files, but typically these geophysical recordings clock in at 10-30 GB. What I do remember, though, was the total transfer size: 4TB. It was kind of like a bunch of .segd, and they were stored in this server cluster that was mounted in a shipping container for easy transport and lifting onboard survey ships. Some geophysics processors needed it on the other side of the world. There were nobody physically heading in the same direction as the transfer, so we figured it would just be easier to rsync it over 4G. It took a little over a week to transfer.

    Normally when we have transfers of a substantial size going far, we ship it on LTO. For short distance transfers we usually run a fiber, and I have no idea how big the largest transfer job has been that way. Must be in the hundreds of TB. The entire cluster is 1.2PB, bit I can’t recall ever having to transfer everything in one go, as the receiving end usually has a lot less space.









  • Depends on your approach, but only open the minimum amount of ports necessary. Fail2ban is a good idea.

    Consider a strict default deny iptables that also affects the output table - in case someone does get in, this will limit the damage one can do by making it part of a botnet.

    Personally I like to isolate any exposed servers on its own vlan, so in case of compromise, it won’t affect any of the other hardware I’m running.

    Also, most routers have less strict security if the connection is coming from the inside. Make sure any access methods to your router is secure.



  • Seconding this. As it’s a mount that is explicitly for your user, you might as well mount it where it’s most convenient for you.

    If, on the other hand, it was a mountpoint for the entire system, I’d keep it in /mnt and go the symlink route - I’m old fashioned, and I like to use /mnt for as much as possible. I find it more tidy that way. On that note, I’m not 100% sold on /media yet