Beiträge von xvlun

    my problem seems to also be fixed in 3.10.1. Thats good enough i think:


    Code
    uname -a
    Linux nas 3.10.1-031001-generic #201307131550 SMP Sat Jul 13 19:51:31 UTC 2013 x86_64 GNU/Linux


    Code
    $  dd if=/dev/zero of=test.img bs=1M count=10480
    10480+0 records in
    10480+0 records out
    10989076480 bytes (11 GB) copied, 119.166 s, 92.2 MB/s


    for comparison cifs still performs better:


    Code
    # dd if=/dev/zero of=test.img bs=1M count=10480
    10480+0 records in
    10480+0 records out
    10989076480 bytes (11 GB) copied, 99.2148 s, 111 MB/s

    back on

    Code
    Linux nas 3.2.0-0.bpo.4-amd64 #1 SMP Debian 3.2.46-1+deb7u1~bpo60+1 x86_64 GNU/Linux


    cifs is working fine:


    Code
    root@nas:~/cifs# dd if=/dev/zero of=test.img bs=1M count=10480
    10480+0 records in
    10480+0 records out
    10989076480 bytes (11 GB) copied, 99.9157 s, 110 MB/s


    the nfs transfer has to be killed on the second run, which takes quite a while:


    Code
    jan@nas:/root/test$  dd if=/dev/zero of=test.img bs=1M count=1048
    1048+0 records in
    1048+0 records out
    1098907648 bytes (1.1 GB) copied, 11.6503 s, 94.3 MB/s
    jan@nas:/root/test$  dd if=/dev/zero of=test.img bs=1M count=1048
    ^C^C^C^C^C^C


    this is iotop during the second try of 1GB:


    Code
    4094 be/4 jan         0.00 B/s    0.00 B/s  0.00 % 99.66 % dd if=/de~count=1048
     1655 be/4 root        0.00 B/s    0.00 B/s  0.00 % 24.43 % [flush-253:0]
     1388 be/3 root        0.00 B/s  117.29 K/s  0.00 % 18.53 % [jbd2/dm-0-8]
     1914 be/4 root        0.00 B/s   31.28 K/s  0.00 % 15.73 % [nfsd]
     1909 be/4 root        0.00 B/s   31.28 K/s  0.00 % 12.12 % [nfsd]
     1912 be/4 root        0.00 B/s   31.28 K/s  0.00 % 12.08 % [nfsd]
     1910 be/4 root        0.00 B/s   31.28 K/s  0.00 % 11.84 % [nfsd]
     1907 be/4 root        0.00 B/s   19.55 K/s  0.00 %  9.34 % [nfsd]
     1905 be/4 root        0.00 B/s    3.91 K/s  0.00 %  1.38 % [nfsd]

    I think it is a kernel bug. The lock up problem is gone using the older kernel. I can repeatedly write to the share without any slowing down of the transfers. Their speed will always be around 55MB/s.


    Code
    jan@nas:/root/test$ uname -a
    Linux nas 2.6.32-5-amd64 #1 SMP Mon Sep 23 22:14:43 UTC 2013 x86_64 GNU/Linux


    Code
    jan@nas:/root/test$ dd if=/dev/zero of=test.img bs=1M count=10480
    10480+0 records in
    10480+0 records out
    10989076480 bytes (11 GB) copied, 200.667 s, 54.8 MB/s


    performance is lacking though: cifs is quite a bit faster:


    Code
    root@nas:~/cifs# dd if=/dev/zero of=test.img bs=1M count=10480
    10480+0 records in
    10480+0 records out
    10989076480 bytes (11 GB) copied, 140.191 s, 78.4 MB/s

    Hi, I have a strange problems with the nfs kernel server, where the machine becomes unresponsive very fast if nfs is used (if nfs is not used for transfers, everything will be fine, cifs works, too.


    my configuration:
    HP N54L, omv 0.5.14, backport 3.2 kernel

    Code
    # /etc/exports: the access control list for filesystems which may be exported
    #               to NFS clients.  See exports(5).
    /media/shares 192.168.1.0/24(rw,crossmnt)


    to test the nfs kernel server i mount this share on the same machine, and try to write to it via dd:


    Code
    /root/test$ dd if=/dev/zero of=test.img bs=1M count=1048
    1048+0 records in
    1048+0 records out
    1098907648 bytes (1.1 GB) copied, 13.6275 s, 80.6 MB/s
    jan@nas:/root/test$ dd if=/dev/zero of=test.img bs=1M count=1048
    ^C^C^C^CKilled


    mostly speed is fine during the first run, but the second will have to be killed because iowait rockets up to 99%, and the command never finishes. Sometimes the system will even get to busy to recognize shutdown events via power button presses...


    dmesg shows some pretty scary messages: Any Ideas?


    the problem with 2. is that i do not know how to make my changes to the smb.conf persistent, i does not even seem possible to link files to the samba config using include, omv will just revert all the changes made if i ever again try to do anything samba related in the web interface (am I wrong?). also allowing samba to follow the links caused unexplicable strange behaviour of omv ;)


    I solved that problem (at least for now) by manually mounting all disks (via the xml config file), as subdirectories of another disk, which i shared via the webinterface.


    At least for me It be a great addition; if it was possible in omv to just add custom directories as samba shares using the web interface. Is there any chance that this feature could be added in the future?

    Hi everybody, currently I have a NAS, which houses a bunch of hdds, which are currently not integrated in a raid setup. Quite often I have to move stuff around from one hdd to another. My problem is that to do this, the data is downloaded from one share on the nas and then reuploaded to the other via the desktop pc, which makes this kind of transfer rather inefficient. So my question(s) would be:


    Is there a way to:
    - achieve that these kind of transfers are handled internally on the nas (without falling back to the command line)
    - and to keep the solution integrated into omv, so that changes in omv would destroy the customizations.

    different computer: no problem at all.


    Code
    dd if=/dev/zero of=/media/jan/SS2TB/tempfile bs=1M count=2048 
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2,1 GB) copied, 19,4719 s, 110 MB/s
    val jan # echo 1 >/proc/sys/vm/drop_caches
    val jan # dd of=/dev/zero if=/media/jan/SS2TB/tempfile bs=1M count=2048 
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2,1 GB) copied, 20,725 s, 104 MB/s


    I also tried to update the firmware of the hdd as I read sth about Problems of the samsung spinpoint F3 drives in combination with the AMD SB 850 chipset but again to no avail. (HP N54L seems to have the AMD RS785E/SB820M, but i tried anyway)


    I give up. I'll buy a new drive

    Zitat von "davidh2k"

    PS: You confused read and write. You read speeds are higher than your write speeds.


    this is read speed, is it not? anyway.
    I did some further testing. And the issue is not software related (as ubuntu 12.04 live shows the same behaviour on the hp n54l). I will put the hdd in a different pc now and try again, if this really makes a differences (as stated above).

    thanks for the suggestions:


    - faulty sata connections on the server side should be excluded as moving the drive around does not change anything.
    - i have not done any specific configuration changes regarding this drive
    - the drive (seems) to work fine in a different computer (running ubuntu 12.04)


    the dd testing results are really really weird. as writing is much faster than reading, but also the writing speed is not really consistent:


    hi, i have a performance problem witn a Samsung HD203WI drive in a HP N54L microserver. While all other installed drives perform reasonably my Samsung drive does not. Transfer speed as measured by hdparm (and real life performance copying files from one drive to another internally or via smb to a different computer) is between 300K/s and 10MB/s (from a 2 TB drive!)


    I have already moved the drives around to exclude a faulty sata connection but to no avail. Also the drive performs normally when installed in a different PC. Any ideas?