Changes to archive do not persist after unmount

Issue #45 closed
Paul Handy created an issue

If I run the following:

$ fuse-zip myziparchive.zip /tmp/zipArchive
$ cp somefile /tmp/zipArchive/path/to/folder/
$ echo sometext >> /tmp/zipArchive/path/to/existing/file
$ fusermount -u /tmp/zipArchive

After I mount it again, I note that it is in its original states - no changes persisted. Am I doing something wrong?

Comments (8)

  1. Alexander Galanin repo owner
    1. check syslog for fuse-zip error messages
    2. wait for fuse-zip process finish after unmounting
  2. Alexander Galanin repo owner

    Or you may run fuse-zip in debug mode (with -d command-line flag) and publish output here.

  3. Paul Handy reporter
    FUSE library version: 2.9.4
    nullpath_ok: 0
    nopath: 0
    utime_omit_ok: 0
    unique: 1, opcode: INIT (26), nodeid: 0, insize: 56, pid: 0
    INIT: 7.23
    flags=0x0003f7fb
    max_readahead=0x00020000
       INIT: 7.19
       flags=0x00000011
       max_readahead=0x00020000
       max_write=0x00020000
       max_background=0
       congestion_threshold=0
       unique: 1, success, outsize: 40
    unique: 2, opcode: LOOKUP (1), nodeid: 1, insize: 49, pid: 31253
    LOOKUP /testdata
    getattr /testdata
       NODEID: 2
       unique: 2, success, outsize: 144
    unique: 3, opcode: LOOKUP (1), nodeid: 2, insize: 45, pid: 31253
    LOOKUP /testdata/some
    getattr /testdata/some
       NODEID: 3
       unique: 3, success, outsize: 144
    unique: 4, opcode: LOOKUP (1), nodeid: 3, insize: 45, pid: 31253
    LOOKUP /testdata/some/file
    getattr /testdata/some/file
       NODEID: 4
       unique: 4, success, outsize: 144
    unique: 5, opcode: OPEN (14), nodeid: 4, insize: 48, pid: 31253
    open flags: 0x8401 /testdata/some/file
       open[35705696] flags: 0x8401 /testdata/some/file
       unique: 5, success, outsize: 32
    unique: 6, opcode: FLUSH (25), nodeid: 4, insize: 64, pid: 31253
    flush[35705696]
       unique: 6, success, outsize: 16
    unique: 7, opcode: GETXATTR (22), nodeid: 4, insize: 68, pid: 31253
    getxattr /testdata/some/file security.capability 0
       unique: 7, error: -95 (Operation not supported), outsize: 16
    unique: 8, opcode: WRITE (16), nodeid: 4, insize: 87, pid: 31253
    write[35705696] 7 bytes to 12 flags: 0x8401
       write[35705696] 7 bytes to 12
       unique: 8, success, outsize: 24
    unique: 9, opcode: FLUSH (25), nodeid: 4, insize: 64, pid: 31253
    flush[35705696]
       unique: 9, success, outsize: 16
    unique: 10, opcode: RELEASE (18), nodeid: 4, insize: 64, pid: 0
    release[35705696] flags: 0x8401
       unique: 10, success, outsize: 16
    unique: 11, opcode: BATCH_FORGET (42), nodeid: 0, insize: 112, pid: 0
    FORGET 4/1
    DELETE: 4
    FORGET 3/1
    DELETE: 3
    FORGET 2/1
    DELETE: 2
    FORGET 1/1
    
  4. Alexander Galanin repo owner

    I don't see anything suspicious in the logs.

    Is directory with archive writable for user running fuse-zip? Is there any fuse-zip related messages in syslog? (for example "Nov 1 18:58:10 box fuse-zip[7574]: Error while closing archive: Failure to create temporary file: Permission denied")

  5. Log in to comment