-
Notifications
You must be signed in to change notification settings - Fork 313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
loopbackfs encountered 'utimensat' error when using cp
#500
Comments
|
can you show an excerpt of the debug log for when this goes wrong? or, even better a test case? |
got:
|
Encountered this too, the symlink itself has timestamps, and tools like Reproducible via: cd /path/to/mnt
ln -s does-not-exist my-smlink
touch -h my-smlink I wonder if the fuse server receives which flag the original call to utimensat used? |
When using
cp -Rp
to copy files into a loopbackfs dir, thecp
command returned error like this.Here's the steps to reproduce:
tar -xf libunistring.tar -C .
It will extract a dir calllib
( libunistring.tar.zip github only allow zip files, the tar file is in the zip, please unzip it firstly)cp -Rp lib <any path in the loopbackfs>
(Note: the -p options is requried)I did some debugging for these case. It seems setattr didn't handle symlink well.
There's a symlink file in the
lib
dir, link to a file beside it. When docp -Rp
, the symlink file created firstly, then SETATTR called on this symlink file. In the handler of setattr,syscall.UtimesNano
called, but the linked file hasn't been created yet, so this system call returns a ENOENT.Environment:
The text was updated successfully, but these errors were encountered: