-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
error adding a file to dvc repo on NAS storage #2818
Comments
Hi @midnightradio ! Could you please show full log for Also, are you sure |
Hi, @efiop There are just a few files in the directory and some verbose messages are following.
|
@midnightradio Hm, weird. Could you show |
@efiop Actually answers for your questions are already shown in the first post, but let me make a double check.
When I do the same operation (init and add) for the same data in local storage, it works well. |
Previously, I missed the last thing @efiop asked me to try and found something interesting this time with trying git on the same directory. Seems the filesystem does not allow to make lock file though the directory has full permission.
|
I think we still should do something about lock. Probably Git is not the best analogy for us in this case. @midnightradio could you elaborate on your case a little bit please? Why do you want to run the repo on a NAS storage directly? |
@midnightradio I meant |
@efiop
Here's the result of the same command ran when working directory is in local storage.
|
@midnightradio Hm, that's interesting. Could you run |
Hi, @shcheklein There's no specific reason for storing data or keeping dvc repo on shared NAS storage. Just accidentally there was not enough space for newly downloaded data on my local disk and I stored them on shared disk. Then I wanted to make dvc remote for the data and tried make dvc repo on the same directory where I stored the data but failed. I don't think this is a bug when git even not allows to initiate a repo on this kind of storage. @efiop Looks like it's a bug to be fixed when
|
As I mentioned previously, I would rather move the data to local space before making a dvc repo when the shared storage even not play well with git. So, I'm ready to close this issue for that point if there's no others who still want to create dvc repo on weird storage more then I did. However, at the point of |
Thanks @midnightradio ! I think both issue are pretty valid. It's a reasonable case when you run For the version issue - yes, let's create a separate ticket and if you can contribute the PR that would be awesome 🙏 We'll try to help you with that. |
@midnightradio, the error in #2818 (comment) is due to I was able to reproduce the same error with: temp=$(mktemp -d)
cd $temp
dvc init --no-scm
mkdir .git
dvc version -v Output is quite similar:
|
@skshetry Thanks for the reproducer! So looks like we are dealing here with a broken |
@skshetry You are right! I tried again with considering your comment, and it turned out the error about I should be more precise. Sorry for my misleading report on |
@midnightradio No worries! Glad you've found the cause! Thank you for the feedback! 🙂 |
Posting this here in case anybody stumbles up on a similar issue in the future. I had this problem on Mac OS when adding a file downloaded from Google Drive. The file was copied with Finder, from a folder exposed by Google Drive for Desktop. For some reason, either Finder or Drive marked the file as locked, which DVC couldn't handle and errored out with an "operation not permitted" error. This problem can be fixed in two ways. If it's a single file, just click "get info" in Finder on that file and remove the locked attribute. If you have many files and that's too much work, use the |
DVC version is 0.62.1 installed by pip on Ubuntu.
I have shared NAS storage mounted on my system and want to create a DVC repo in the storage.
I could successfully initialized a repo by dvc init command, but adding a file fails with an error message shown below.
The text was updated successfully, but these errors were encountered: