{
  "id": 228548,
  "title": "Read-only input?",
  "url": "/competitions/plant-pathology-2021-fgvc8/discussion/228548",
  "author_name": "",
  "post_date": "2021-03-25T07:50:39.303529200Z",
  "votes": 2,
  "comment_count": 2,
  "views": 0,
  "content": "<p>OSError: [Errno 30] Read-only file system: '/kaggle/input/plant-pathology-2021-fgvc8/train_images/800113bb65efe69e.jpg'</p>\n<p>Keep getting this error when trying to copy (using shutil.copy2) the files in train_images from the input directory to a new folder in the working directory. I don't know what's going on but I was able to do it before on the same exact kernel without getting this error. Tried deleting my notebooks and creating new ones for this challenge already but am still getting the same error. Anyone else experiencing this?</p>",
  "messages": [
    {
      "id": "1251858",
      "postDate": "03/25/2021 07:50:39",
      "content": "<p>OSError: [Errno 30] Read-only file system: '/kaggle/input/plant-pathology-2021-fgvc8/train_images/800113bb65efe69e.jpg'</p>\n<p>Keep getting this error when trying to copy (using shutil.copy2) the files in train_images from the input directory to a new folder in the working directory. I don't know what's going on but I was able to do it before on the same exact kernel without getting this error. Tried deleting my notebooks and creating new ones for this challenge already but am still getting the same error. Anyone else experiencing this?</p>",
      "rawMarkdown": "OSError: [Errno 30] Read-only file system: '/kaggle/input/plant-pathology-2021-fgvc8/train_images/800113bb65efe69e.jpg'\n\n\nKeep getting this error when trying to copy (using shutil.copy2) the files in train_images from the input directory to a new folder in the working directory. I don't know what's going on but I was able to do it before on the same exact kernel without getting this error. Tried deleting my notebooks and creating new ones for this challenge already but am still getting the same error. Anyone else experiencing this?",
      "votes": null
    },
    {
      "id": "1251892",
      "postDate": "03/25/2021 08:28:48",
      "content": "<p>It seems like due to a mistake in your code you're trying to copy files from the <code>/kaggle/input</code> directory to a new place that is still under the <code>/kaggle/input</code> directory, which is not allowed. You can however copy your files to the <code>/kaggle/working</code> directory (all files there would be saved when creating a Run&amp;Commit version) or create a new directory (e.g. <code>/kaggle/tmp</code>) for temp usage and store files there.</p>",
      "rawMarkdown": "It seems like due to a mistake in your code you're trying to copy files from the `/kaggle/input` directory to a new place that is still under the `/kaggle/input` directory, which is not allowed. You can however copy your files to the `/kaggle/working` directory (all files there would be saved when creating a Run&Commit version) or create a new directory (e.g. `/kaggle/tmp`) for temp usage and store files there.",
      "votes": null
    },
    {
      "id": "1252070",
      "postDate": "03/25/2021 12:02:08",
      "content": "<p>Thanks for the response. However, I double checked through printing the path where I'm sending it to and I am indeed sending it to the /kaggle/working directory. For instance, here's one of the paths: \"/kaggle/working/plants-training/frog_eye_leaf_spot\". I can also see the plants-training and the frog_eye_leaf_spot subdirectories through the data tab on the right meaning I know for sure that they have been successfully created under the /kaggle/working directory. Seems that this issue also occurs with other challenges and I found that some were able to fix by deleting their notebooks and recreating their code on completely new kernels. Unfortunately, it did not solve mine. Will try to use the temp directory just in case. Thank you :(</p>",
      "rawMarkdown": "Thanks for the response. However, I double checked through printing the path where I'm sending it to and I am indeed sending it to the /kaggle/working directory. For instance, here's one of the paths: \"/kaggle/working/plants-training/frog_eye_leaf_spot\". I can also see the plants-training and the frog_eye_leaf_spot subdirectories through the data tab on the right meaning I know for sure that they have been successfully created under the /kaggle/working directory. Seems that this issue also occurs with other challenges and I found that some were able to fix by deleting their notebooks and recreating their code on completely new kernels. Unfortunately, it did not solve mine. Will try to use the temp directory just in case. Thank you :(",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 1251892,
      "author_name": "nickuzmenkov",
      "author_url": "",
      "post_date": "03/25/2021 08:28:48",
      "content": "<p>It seems like due to a mistake in your code you're trying to copy files from the <code>/kaggle/input</code> directory to a new place that is still under the <code>/kaggle/input</code> directory, which is not allowed. You can however copy your files to the <code>/kaggle/working</code> directory (all files there would be saved when creating a Run&amp;Commit version) or create a new directory (e.g. <code>/kaggle/tmp</code>) for temp usage and store files there.</p>",
      "votes": null,
      "replies": [
        {
          "id": 1252070,
          "author_name": "chummicrisologo",
          "author_url": "",
          "post_date": "03/25/2021 12:02:08",
          "content": "<p>Thanks for the response. However, I double checked through printing the path where I'm sending it to and I am indeed sending it to the /kaggle/working directory. For instance, here's one of the paths: \"/kaggle/working/plants-training/frog_eye_leaf_spot\". I can also see the plants-training and the frog_eye_leaf_spot subdirectories through the data tab on the right meaning I know for sure that they have been successfully created under the /kaggle/working directory. Seems that this issue also occurs with other challenges and I found that some were able to fix by deleting their notebooks and recreating their code on completely new kernels. Unfortunately, it did not solve mine. Will try to use the temp directory just in case. Thank you :(</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "1251858": "OSError: [Errno 30] Read-only file system: '/kaggle/input/plant-pathology-2021-fgvc8/train_images/800113bb65efe69e.jpg'\n\n\nKeep getting this error when trying to copy (using shutil.copy2) the files in train_images from the input directory to a new folder in the working directory. I don't know what's going on but I was able to do it before on the same exact kernel without getting this error. Tried deleting my notebooks and creating new ones for this challenge already but am still getting the same error. Anyone else experiencing this?",
    "1251892": "It seems like due to a mistake in your code you're trying to copy files from the `/kaggle/input` directory to a new place that is still under the `/kaggle/input` directory, which is not allowed. You can however copy your files to the `/kaggle/working` directory (all files there would be saved when creating a Run&Commit version) or create a new directory (e.g. `/kaggle/tmp`) for temp usage and store files there.",
    "1252070": "Thanks for the response. However, I double checked through printing the path where I'm sending it to and I am indeed sending it to the /kaggle/working directory. For instance, here's one of the paths: \"/kaggle/working/plants-training/frog_eye_leaf_spot\". I can also see the plants-training and the frog_eye_leaf_spot subdirectories through the data tab on the right meaning I know for sure that they have been successfully created under the /kaggle/working directory. Seems that this issue also occurs with other challenges and I found that some were able to fix by deleting their notebooks and recreating their code on completely new kernels. Unfortunately, it did not solve mine. Will try to use the temp directory just in case. Thank you :("
  },
  "source": "meta"
}