search

yadayada / acd_cli

An unmaintained command line interface and FUSE filesystem for Amazon (Cloud) Drive
Other
1.35k stars 165 forks source link

Unable to create LVM2 physical volume #371

Open ni3que opened 8 years ago

ni3que commented 8 years ago

Unfortunately its not possible to create a physical volume over a file which is stored on ACD and mounted via ACDFuse and loopback interface.

I got follwing error:

16-08-04 09:43:13.930 [DEBUG] [acdcli.acd_fuse] - -> getxattr /vserver1/backup0.img ('security.capability',)
16-08-04 09:43:13.939 [DEBUG] [acdcli.acd_fuse] - <- getxattr '[Errno 61] No data available'
16-08-04 09:43:13.940 [DEBUG] [acdcli.acd_fuse] - -> write /vserver1/backup0.img (4096, 4096, 2)
16-08-04 09:43:13.941 [ERROR] [acdcli.acd_fuse] - Wrong offset for writing to fh 2.
16-08-04 09:43:13.941 [DEBUG] [acdcli.acd_fuse] - <- write '[Errno 14] Bad address'

Any ideas?

Thanks & regard, Marko

yadayada commented 8 years ago

Only sequential (over)writes are supported, so that write at offset 4096 fails.

bgemmill commented 8 years ago

ni3que, if you look at more of your log, does LVM2's writing pattern look like the issue I was having with ecryptfs? https://github.com/yadayada/acd_cli/issues/368

If so, I'm nearing completion on a PR that will allow for sequential writing using multiple file handles instead of requiring just one.

edit: yadayada, I didn't hear back in the other issue, is this a feature you'd be interested in?

yadayada commented 8 years ago

@bgemmill I guess writing on the current offset from different file handles will not have detrimental effects on standard write operations. If you make a PR, I probably will have a look at it on the weekend.