FAQ
Hello,

since we updated our SVN-Server to version 1.7.0 we're no longer able to
execute commands through samba mounted shares.
Commands through our LAN is still working.

For example:

# /usr/home/michael/mnt/websites.sh

Content from website.sh:

mount_smbfs -N -I 192.168.23.225 -E utf-8:cp1252
//fausten@KALI-FILES/pw-websites /usr/home/michael/mount/pw-websites

utf8:cp1252 option is needed, otherwise the German umlauts are broken on
the share.

% cd /usr/home/michael/mount/pw-websites/path/to/my/website
% svn status -u

svn: E200030: sqlite: disk I/O error
svn: E200030: sqlite: disk I/O error

On my PC (locally) svn just works fine. I use a FreeBSD 9.0 amd64
machine with, since today subversion 1.7.5, but the error
still occurs.

Builded subversion with (Compiler Options):

P4_STYLE_MARKERS
ENHANCED_KEYWORD
FREEBSD_TEMPLATE
NEON

- No private modifications

Our server uses FreeBSD 8.2 with Subversion 1.7.5.

Search Discussions

  • Philip Martin at May 21, 2012 at 10:58 am

    Michael Fausten writes:

    since we updated our SVN-Server to version 1.7.0 we're no longer able
    to execute commands through samba mounted shares.
    Commands through our LAN is still working.

    For example:

    # /usr/home/michael/mnt/websites.sh

    Content from website.sh:

    mount_smbfs -N -I 192.168.23.225 -E utf-8:cp1252
    //fausten@KALI-FILES/pw-websites /usr/home/michael/mount/pw-websites

    utf8:cp1252 option is needed, otherwise the German umlauts are broken
    on the share.

    % cd /usr/home/michael/mount/pw-websites/path/to/my/website
    % svn status -u

    svn: E200030: sqlite: disk I/O error
    svn: E200030: sqlite: disk I/O error

    On my PC (locally) svn just works fine. I use a FreeBSD 9.0 amd64
    machine with, since today subversion 1.7.5, but the error
    still occurs.

    Builded subversion with (Compiler Options):

    P4_STYLE_MARKERS
    ENHANCED_KEYWORD
    FREEBSD_TEMPLATE
    NEON

    - No private modifications

    Our server uses FreeBSD 8.2 with Subversion 1.7.5.
    Let me see if I understand:

    - you have a working copy on a Samba network disk

    - the Samba server is FreeBSD 8.2

    - the Samba client is FreeBSD 9.0

    On Linux I'd run "strace svn st -u" to find out which system call is
    failing. Do you have strace installed? Perhaps truss can provide the
    information?

    It appears that your Samba setup doesn't support some POSIX sematics.
    Perhaps mounting nobrl will help?

    --
    Philip
  • Michael Fausten at May 22, 2012 at 12:29 pm

    On 21.05.2012 12:58, Philip Martin wrote:
    Michael Fausten<fausten@pw-internet.de> writes:
    since we updated our SVN-Server to version 1.7.0 we're no longer able
    to execute commands through samba mounted shares.
    Commands through our LAN is still working.

    For example:

    # /usr/home/michael/mnt/websites.sh

    Content from website.sh:

    mount_smbfs -N -I 192.168.23.225 -E utf-8:cp1252
    //fausten@KALI-FILES/pw-websites /usr/home/michael/mount/pw-websites

    utf8:cp1252 option is needed, otherwise the German umlauts are broken
    on the share.

    % cd /usr/home/michael/mount/pw-websites/path/to/my/website
    % svn status -u

    svn: E200030: sqlite: disk I/O error
    svn: E200030: sqlite: disk I/O error

    On my PC (locally) svn just works fine. I use a FreeBSD 9.0 amd64
    machine with, since today subversion 1.7.5, but the error
    still occurs.

    Builded subversion with (Compiler Options):

    P4_STYLE_MARKERS
    ENHANCED_KEYWORD
    FREEBSD_TEMPLATE
    NEON

    - No private modifications

    Our server uses FreeBSD 8.2 with Subversion 1.7.5.
    Let me see if I understand:

    - you have a working copy on a Samba network disk

    - the Samba server is FreeBSD 8.2

    - the Samba client is FreeBSD 9.0
    This is correct.
    On Linux I'd run "strace svn st -u" to find out which system call is
    failing. Do you have strace installed? Perhaps truss can provide the
    information?
    No I don't. strace is only for i386 while I'm running amd64. DTrace
    isn't also an option for me, because I would need to rebuild my kernel.
    But I'm just a beginner, so I don't think this would end well :)
    I tried truss, but I can't do anything with the results. Maybe
    they are interesting for you?

    http://www.file-upload.net/download-4381573/truss.log.html
    It appears that your Samba setup doesn't support some POSIX sematics.
    Perhaps mounting nobrl will help?
    Unfortunately mount_smbfs doesn't support the nobrl option.
  • Les Mikesell at May 22, 2012 at 12:48 pm

    On Tue, May 22, 2012 at 7:28 AM, Michael Fausten wrote:
    - the Samba server is FreeBSD 8.2

    - the Samba client is FreeBSD 9.0

    This is correct.
    It seems odd in general to use samba between unix-type machines
    instead of nfs - or just using ssh, remote X, or freenx to log into
    the machine that has the disk space. Can you use nfs instead (you can
    still share the same space with samba if there are also windows
    clients) ?
    It appears that your Samba setup doesn't support some POSIX sematics.
    Perhaps mounting nobrl will help?
    Unfortunately mount_smbfs doesn't support the nobrl option.
    Linux has a cifs mount option that preserves more of the unix
    semantics than smb, but I don't know if that exists in freebsd.

    --
    Les Mikesell
    lesmikesell@gmail.com
  • Philip Martin at May 22, 2012 at 3:09 pm

    Michael Fausten writes:

    Let me see if I understand:

    - you have a working copy on a Samba network disk

    - the Samba server is FreeBSD 8.2

    - the Samba client is FreeBSD 9.0
    This is correct.
    On Linux I'd run "strace svn st -u" to find out which system call is
    failing. Do you have strace installed? Perhaps truss can provide the
    information?
    No I don't. strace is only for i386 while I'm running amd64. DTrace
    isn't also an option for me, because I would need to rebuild my kernel.
    But I'm just a beginner, so I don't think this would end well :)
    I tried truss, but I can't do anything with the results. Maybe
    they are interesting for you?

    http://www.file-upload.net/download-4381573/truss.log.html
    It's something to do with locking:

    open("/usr/home/michael/mount/pw-websites/PW-Websites/baumarkt.de/Website-online
    /.svn/wc.db",O_RDWR|0x100000,00) = 3 (0x3)

    [...]

    fcntl(3,F_SETLK,0x7fffffffbaf0) = 0 (0x0)
    fcntl(3,F_SETLK,0x7fffffffc2a0) = 0 (0x0)
    fcntl(3,F_SETLK,0x7fffffffc2a0) ERR#11 'Resource deadlock avoid
    ed'
    fcntl(3,F_SETLK,0x7fffffffc2a0) = 0 (0x0)
    write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)
    write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)
    It appears that your Samba setup doesn't support some POSIX sematics.
    Perhaps mounting nobrl will help?
    Unfortunately mount_smbfs doesn't support the nobrl option.
    I suspect that sqlite is attempting byte range locking and your server
    doesn't support it. I don't know what to do about that.

    --
    Philip
  • Daniel Shahaf at May 23, 2012 at 7:35 am

    Philip Martin wrote on Tue, May 22, 2012 at 16:09:09 +0100:
    Michael Fausten <fausten@pw-internet.de> writes:
    Let me see if I understand:

    - you have a working copy on a Samba network disk

    - the Samba server is FreeBSD 8.2

    - the Samba client is FreeBSD 9.0
    This is correct.
    On Linux I'd run "strace svn st -u" to find out which system call is
    failing. Do you have strace installed? Perhaps truss can provide the
    information?
    No I don't. strace is only for i386 while I'm running amd64. DTrace
    isn't also an option for me, because I would need to rebuild my kernel.
    But I'm just a beginner, so I don't think this would end well :)
    I tried truss, but I can't do anything with the results. Maybe
    they are interesting for you?

    http://www.file-upload.net/download-4381573/truss.log.html
    It's something to do with locking:

    open("/usr/home/michael/mount/pw-websites/PW-Websites/baumarkt.de/Website-online
    /.svn/wc.db",O_RDWR|0x100000,00) = 3 (0x3)

    [...]

    fcntl(3,F_SETLK,0x7fffffffbaf0) = 0 (0x0)
    fcntl(3,F_SETLK,0x7fffffffc2a0) = 0 (0x0)
    fcntl(3,F_SETLK,0x7fffffffc2a0) ERR#11 'Resource deadlock avoid
    ed'
    fcntl(3,F_SETLK,0x7fffffffc2a0) = 0 (0x0)
    write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)
    write(2,"svn: E200030: sqlite: disk I/O e"...,37) = 37 (0x25)
    It appears that your Samba setup doesn't support some POSIX sematics.
    Perhaps mounting nobrl will help?
    Unfortunately mount_smbfs doesn't support the nobrl option.
    I suspect that sqlite is attempting byte range locking and your server
    doesn't support it. I don't know what to do about that.
    Perhaps tell sqlite to use a different locking strategy by default?

    (I know the default strategy can be set at compile-time. I don't recall
    whether it can also be set later.)
  • Niemann, Hartmut at May 21, 2012 at 11:23 am
    Hello Michael,

    Do you have a virus scanner involved?
    Try to disable it, just for the tests.

    I have seen the virus scanner interfere with
    the sqlite engine of subversion 1.7.x in very interesing ways.
    The new (1.7.0) sqlite-based client writes some journal file into
    the working copy, which may fail if the virus scanner takes too long
    to check the file.
    In my case a subsequent fopen() call fails, which is being reported as sqlite
    disk IO errors.

    I have written a small C program that does
    fopen()
    write several k of data
    fclose()
    and repeat.
    My box normally fails within 100..1000 iterations ... it takes some
    time to trigger it, but *very* rarely it has made all 64000 iterations
    without error.
    Interestingly, it is fopen() that fails with EINVAL.

    Mit freundlichen Grüßen
    Dr.
    Hartmut Niemann

    Siemens AG
    Infrastructure & Cities Sector
    Rail Systems Division
    Locomotives and Components
    IC RL LOC EN LE 8
    Werner-von-Siemens-Str. 67
    91052 Erlangen, Deutschland
    Tel.: +49 9131 7-34264
    Fax: +49 9131 7-26254
    mailto:hartmut.niemann@siemens.com

    Siemens Aktiengesellschaft: Vorsitzender des Aufsichtsrats: Gerhard Cromme; Vorstand: Peter Löscher, Vorsitzender; Roland Busch, Brigitte Ederer, Klaus Helmrich, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen, Michael Süß; Sitz der Gesellschaft: Berlin und München, Deutschland; Registergericht: Berlin Charlottenburg, HRB 12300, München, HRB 6684; WEEE-Reg.-Nr. DE 23691322

    -----Ursprüngliche Nachricht-----
    Von: Michael Fausten
    Gesendet: Montag, 21. Mai 2012 12:20
    An: users@subversion.apache.org
    Betreff: Can't execute svn commands through the network

    Hello,

    since we updated our SVN-Server to version 1.7.0 we're no
    longer able to
    execute commands through samba mounted shares.
    Commands through our LAN is still working.

    For example:

    # /usr/home/michael/mnt/websites.sh

    Content from website.sh:

    mount_smbfs -N -I 192.168.23.225 -E utf-8:cp1252
    //fausten@KALI-FILES/pw-websites /usr/home/michael/mount/pw-websites

    utf8:cp1252 option is needed, otherwise the German umlauts
    are broken on
    the share.

    % cd /usr/home/michael/mount/pw-websites/path/to/my/website
    % svn status -u

    svn: E200030: sqlite: disk I/O error
    svn: E200030: sqlite: disk I/O error

    On my PC (locally) svn just works fine. I use a FreeBSD 9.0 amd64
    machine with, since today subversion 1.7.5, but the error
    still occurs.

    Builded subversion with (Compiler Options):

    P4_STYLE_MARKERS
    ENHANCED_KEYWORD
    FREEBSD_TEMPLATE
    NEON

    - No private modifications

    Our server uses FreeBSD 8.2 with Subversion 1.7.5.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupusers @
categoriessubversion
postedMay 21, '12 at 10:26a
activeMay 23, '12 at 7:35a
posts7
users5
websitesubversion.apache.org
irc#svn

People

Translate

site design / logo © 2022 Grokbase