Beiträge von darkarn

  • Slow Performance on SMB Network Drive

    I went ahead with using another OMV host as the iperf client. Here's the results when the OMV host that is the iperf server does not have the Intel NIC (I will install that tonight due to some family stuff I need to go to):


    ------------------------------------------------------------
    Server listening on TCP port 12345
    TCP window size: 85.3 KByte (default)
    ------------------------------------------------------------
    [ 4] local 192.168.1.21 port 12345 connected with 192.168.1.22 port 60764
    [ ID] Interval Transfer Bandwidth
    [ 4] 0.0- 0.9 sec 100 MBytes 924 Mbits/sec
    [ 5] local 192.168.1.21 port 12345 connected with 192.168.1.22 port 60768
    [ 5] 0.0- 8.9 sec 1000 MBytes 938 Mbits/sec
    [ 4] local 192.168.1.21 port 12345 connected with 192.168.1.22 port 60770
    [ 4] 0.0-89.2 sec 9.77 GBytes 941 Mbits/sec
    [ 5] local 192.168.1.21 port 12345 connected with 192.168.1.22 port 60800
    [ 5] 0.0- 9.2 sec 1.00 GBytes 936 Mbits/sec
    [ 4] local 192.168.1.21 port 12345 connected with 192.168.1.22 port 60866
    [ 4] 0.0-912.5 sec 100 GBytes 941 Mbits/sec

  • Slow Performance on SMB Network Drive

    Zitat von ryecoaaron

    iperf for network speed. Large files for samba speed.


    Thanks, without the Intel NIC, I am getting 40 MB/s for samba speed when copying from server to client like my computer, 90 MB/s for copying from client to server. As for iperf, I cannot do this yet as I do not have a Linux computer as a client (as per detailed here: how to find bottlenecks and increase write/read speeds ) I am unsure if another OMV host will be ok for this.

  • Slow Performance on SMB Network Drive

    Zitat von ryecoaaron

    I guess. In most situations, it is just the NIC and file size. Some systems need server settings but I have never had to change a setting on the client. cpu/ram only come into play if you are using an arm board. Most newer hard drives are fast enough to saturate gigabit. So, they typically aren't the issue either.


    Hmm I see. What tests should I do in the meantime? I see many commands but not sure what is for what...

  • Slow Performance on SMB Network Drive

    Zitat von ryecoaaron

    No max protocol or min protocol settings? I actually don't use any settings for my samba setups and they saturate gigabit.


    In your list, file size is the largest factor. Small files will never transfer as fast as large files.


    I recalled that using the max/min protocol settings caused some of my SMB shares to be unconnectable at all but I can try again.


    And ah yes, I forgot about file size but are the rest of the factors in the list correct?

  • Slow Performance on SMB Network Drive

    Currently I am using these settings too:


    which seems to work better than my initial settings:

    Code
    socket options = TCP_NODELAY SO_RCVBUF=65536 SO_SNDBUF=65536
read raw = yes 
write raw = yes 
max xmit = 65535 
dead time = 15
getwd cache = yes

    I am unsure why, let me monitor further before making up my conclusion about settings.


    But in the meantime, am I right to say that the following will affect SMB speeds (top = biggest factor, bottom = lowest factor)?:


    1. Server SMB settings
    2. NIC
    3. Client SMB settings
    4. HDD speeds
    5. CPU/RAM

  • Slow Performance on SMB Network Drive

    Weird, those tweaks went missing so I put them back in. Let's see how it goes. As for upgrading to Samba 4, it looks like the command

    Code
    apt-get -t wheezy-backports install samba=2:4.1.17+dfsg-1~bpo70+1

    won't work in OMV 3; I think it needs to be tweaked for Jessie.


    Meanwhile, will those hardware I mentioned help/hinder SMB speeds?

  • Slow Performance on SMB Network Drive

    I am using a Windows 7 computer with another OMV rig that has a Samba share.


    I noticed that whenever I play music (FLACs) and edit photos (RAW/CR2) using Adobe Lightroom such that these music and photos files are on the same Samba network drive, the music will be quite laggy and the photo editing will be unusually slow at the same time.


    I am suspecting a few causes such as:
    1. My computer being on Windows 7 instead of 10, which means I cannot use Samba 3
    2. My OMV rig using a Realtek NIC instead of an Intel NIC
    3. My OMV rig is lacking in other ways (e.g. lack of RAM or CPU?)


    Where should I start in figuring out the cause of the problem?

  • Haswell i3 Build for NAS + Light VM Duties: Will this work?

    Hi! Now with quite a long while of using OMV and having even two OMV hosts but on extremely old (and in the case for one of them, loaned) hardware (Core 2 era stuff), I think it is time for me to build something more proper!


    Here's my OMV hosts:
    Main Host (to be replaced. NAS duties (e.g. Plex, SMB) and light VM usage (about 3 to 5 LAMP VMs in Virtualbox)
    Core 2 Duo E7500
    4 GB DDR2 RAM running at 800 Mhz
    MSI G31TM-P31 (4 SATA 3.0GB/s ports)
    Intel Dual Port Gigabit NIC


    HGST HTS721010A9E630 (1TB) (SATA 3.0GB/s) (OS drive, partitioned to have data too)
    Seagate ST1000DM005 HD103SJ (1TB) (SATA 3.0GB/s)
    SAMSUNG HD103SJ (1TB) (SATA 3.0GB/s)
    Hitachi HDS723030ALA640 (3TB) (SATA 3.0GB/s)


    Snapshot Host (just for holding rsnapshots of the main data pool)
    Core 2 Quad Q6600
    6 GB DDR2 RAM running at 667 Mhz
    Asus P5KR (5 SATA 3.0GB/s ports, 1 eSATA port)
    Intel Single Port Gigabit NIC


    TOSHIBA MK3263GSX (320GB) (eSATA) (OS drive)
    Seagate ST2000DL004 HD204UI (2TB) (SATA 3.0GB/s)
    Toshiba DT01ACA300 (3TB) (SATA 3.0GB/s)
    HGST (750 GB) (SATA 3.0GB/s)


    After some reading up online, here's what I am thinking of, based on what I can get locally in Singapore due to warranty purposes:


    CPU (+GPU since integrated): Haswell i3-4170
    Apparently, this is the only Haswell i3 left in the market so I would have to stick with this. It doesn't seem too bad given that FreeNAS guides are recommending Haswell i3s too due to the AES-NI capability.


    Motherboard: ASROCKRACK Motherboard H97M WS
    I decided on something more server grade and chanced upon this motherboard. It has two Intel NICs, which means no more using NIC cards, and 6 SATA 6.0GB/s ports which is sufficient for one OMV host. I have also considered other options like ASROCK Motherboard Z97M WS, ASROCKRACK Motherboard E3C222D4U and ASROCKRACK Motherboard E3C224 but they seem too pricey and may need more expensive ECC RAMs.


    RAM: 8GB 1600MHz Kingston RAM Non-ECC
    I am aware that ECC RAMs are important but the markup here is simply too great (2x!). If I can find better sources this may change.


    PSU: 500W
    I have not decided on the brand and model yet but I can at least say that I will need about 500W at most.


    Casing: ATX Casing
    While the motherboard I am choosing is micro-ATX, having an ATX casing means more airflow and more HDD bays.


    Will this be sufficient for my usage? Thanks!

  • [GUIDE] Rsnapshot From One OMV Host to Another OMV Host Using Command Line

    Rsnapshot From One OMV Host to Another OMV Host Using Command Line



    Description
    This little tutorial describes how to use rsnapshot on an OMV host (hereby referred to as "Backup Host") to directly do snapshot backups of data residing on another OMV host (hereby referred to as "Main Host").
    In other words, you will not need to rsnapshot onto "Main Host" first and then transfer the snapshots to "Backup Host" via rsync (or any other method).
    This can be useful for those who prefer to keep snapshots and the data on separate hosts due to various reasons (mine was the lack of HDD space and SATA ports in any of the hosts) and if the remoteshare plugin does not work (which is fixed in OMV 3).


    Requirements
    - Two OMV Hosts (preferably fully updated, same OMV versions)
    - Both connected in a LAN
    - Being willing and able to work with command line (e.g. PUTTY)


    Procedure

    • Keep in mind that rsnapshot is a pull-based design; the "Backup Host" running it will pull the data from the "Main Host" (see links 1 and 2). You can't push data from the "Main Host" in other words.
    • In "Main Host", use OMV GUI to create SMB share of the data you want snapshots of (You may also use other network sharing protocols like NFS but I have yet to try this)
    • (Optional) In "Backup Host", use OMV GUI to create SMB share to contain the snapshots (You may also use other network sharing protocols like NFS but I have yet to try this)
    • In both hosts, install the Rsnapshot plugin using the OMV GUI
    • In both hosts, enable SSH using the SSH plugin in the OMV GUI
    • Open two command line windows, one for the "Backup Host" and another for the "Main Host"
    • In both hosts, execute "sudo apt-get install cifs-utils" or equivalent for the network protocol used (see link 3)
    • In "Backup Host", make a mount point (e.g. sudo mkdir /media/samba) (see link 4)
    • In "Backup Host", open /etc/fstab with your text editor (e.g. sudo nano /etc/fstab/)
    • Add the share of the "Main Host" in the last line of fstab (e.g. //192.168.1.21/test /media/samba cifs defaults,credentials=/etc/samba/credentials 0 0) (see link 4)
    • In "Backup Host", create /etc/samba/credentials with your text editor (e.g. sudo nano /etc/samba/credentials)
    • Add the credentials of the share like this into /etc/samba/credentials and save: username=[your username]password=[your password]
    • In "Backup Host", make the file owned by root and ro by root (e.g. sudo chown root.root /etc/samba/credentials && sudo chmod 400 /etc/samba/credentials) (see link 4)
    • In "Backup Host", execute "mount -a" to mount the share of "Main Host" (or you may restart "Backup Host")
    • In "Backup Host", open /etc/rsnapshot.conf with your text editor (e.g. sudo nano /etc/rsnapshot.conf)
    • Edit snapshot_root to where in "Backup Host" you want to save the snapshots to
    • Edit the backup points to point to the share of "Main Host" (e.g. /media/samba/ test/)
    • Edit any other parts as you see fit
    • Save rsnapshot.conf
    • In "Backup Host", execute "rsnapshot configtest" and "rsnapshot -t hourly" to test
    • Finally, execute "rsnapshot hourly" to perform the actual snapshot! (Or you may even cron this as you see fit)


    References
    1. http://askubuntu.com/questions…he-server-from-the-client
    2. https://www.digitalocean.com/c…rsnapshot-on-ubuntu-12-04
    3. https://askubuntu.com/question…d-superblock-error/525246
    4. https://help.ubuntu.com/community/Fstab

  • Baremetal OMV or OMV as a VM in ESXi?

    Update: I have 2 VMs running in the VirtualBox (nextcloud and OMV 3.x) in OMV now, all seems good so far.


    I may just consolidate the VMs further into this configuration:


    1 VM for outward facing duties (e.g. two separate instances of nextcloud). Will use Apache's Virtual Host to help in this


    1 VM for web development purpose; will not be exposed to the Internet. Will use Apache's Virtual Host to help in this


    1-3 VMs for playing around with; will not be exposed to the Internet too


    Meanwhile, looks like I will need better HDDs or better CPU+mobo+RAM combos; I am having performance issues when playing music from the OMV NAS and also do other duties with it like transferring of certain files