{
  "id": 166252,
  "title": "No space left on device",
  "url": "/competitions/birdsong-recognition/discussion/166252",
  "author_name": "",
  "post_date": "2020-07-12T09:56:25.205448800Z",
  "votes": 1,
  "comment_count": 3,
  "views": 0,
  "content": "<p>OSError: [Errno 28] No space left on device\n<img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F3004733%2F95a669426afa3d55431e3c1f64926477%2FScreenshot%202020-07-12%20at%202.30.01%20PM.png?generation=1594544435440970&amp;alt=media\" alt=\"\">\nMy HDD is getting fulled. How can I resolve this\n( I am new to kaggle) </p>\n\n<p>I found a solution\n<code>%env JOBLIB_TEMP_FOLDER=/tmp\n</code>\nbut I don't know what does it mean. Help!</p>",
  "messages": [
    {
      "id": "925771",
      "postDate": "07/12/2020 09:56:25",
      "content": "<p>OSError: [Errno 28] No space left on device\n<img src=\"https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F3004733%2F95a669426afa3d55431e3c1f64926477%2FScreenshot%202020-07-12%20at%202.30.01%20PM.png?generation=1594544435440970&amp;alt=media\" alt=\"\">\nMy HDD is getting fulled. How can I resolve this\n( I am new to kaggle) </p>\n\n<p>I found a solution\n<code>%env JOBLIB_TEMP_FOLDER=/tmp\n</code>\nbut I don't know what does it mean. Help!</p>",
      "rawMarkdown": "OSError: [Errno 28] No space left on device\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F3004733%2F95a669426afa3d55431e3c1f64926477%2FScreenshot%202020-07-12%20at%202.30.01%20PM.png?generation=1594544435440970&amp;alt=media)\nMy HDD is getting fulled. How can I resolve this\n( I am new to kaggle) \n\nI found a solution\n`%env JOBLIB_TEMP_FOLDER=/tmp\n`\nbut I don't know what does it mean. Help!",
      "votes": null
    },
    {
      "id": "925862",
      "postDate": "07/12/2020 10:55:18",
      "content": "<p>It is difficult to understand what is causing this problem without having a look at the actual code. You can share the notebook for analysis. However, You can check whether you are writing some file here or saving the processed image here. </p>\n\n<p>You can check the contents of the output directory.  </p>",
      "rawMarkdown": "It is difficult to understand what is causing this problem without having a look at the actual code. You can share the notebook for analysis. However, You can check whether you are writing some file here or saving the processed image here. \n\nYou can check the contents of the output directory.",
      "votes": null
    },
    {
      "id": "925882",
      "postDate": "07/12/2020 11:09:03",
      "content": "<p>I was splitting the data and making new files of that and HDD(hard drive) of kaggle is filled as new memory is filling. Kaggle HDD limit is 5GB (as you can see in the image).\nNow I am thinking to do in parts and combining them.</p>",
      "rawMarkdown": "I was splitting the data and making new files of that and HDD(hard drive) of kaggle is filled as new memory is filling. Kaggle HDD limit is 5GB (as you can see in the image).\nNow I am thinking to do in parts and combining them.",
      "votes": null
    },
    {
      "id": "925956",
      "postDate": "07/12/2020 11:54:22",
      "content": "<p>Yes unfortunately splitting is the only way to overcome this limitation.\nThe <code>%env JOBLIB_TEMP_FOLDER=/tmp</code> writes the files generated by the joblib library in the /tmp folder instead of the current working folder, it is useful only if you are using the joblib library or any library you are using uses joblil, for example sklearn.</p>",
      "rawMarkdown": "Yes unfortunately splitting is the only way to overcome this limitation.\nThe ` %env JOBLIB_TEMP_FOLDER=/tmp ` writes the files generated by the joblib library in the /tmp folder instead of the current working folder, it is useful only if you are using the joblib library or any library you are using uses joblil, for example sklearn.",
      "votes": null
    }
  ],
  "comments": [
    {
      "id": 925862,
      "author_name": "redwankarimsony",
      "author_url": "",
      "post_date": "07/12/2020 10:55:18",
      "content": "<p>It is difficult to understand what is causing this problem without having a look at the actual code. You can share the notebook for analysis. However, You can check whether you are writing some file here or saving the processed image here. </p>\n\n<p>You can check the contents of the output directory.  </p>",
      "votes": null,
      "replies": [
        {
          "id": 925882,
          "author_name": "jainarindam",
          "author_url": "",
          "post_date": "07/12/2020 11:09:03",
          "content": "<p>I was splitting the data and making new files of that and HDD(hard drive) of kaggle is filled as new memory is filling. Kaggle HDD limit is 5GB (as you can see in the image).\nNow I am thinking to do in parts and combining them.</p>",
          "votes": null,
          "replies": []
        },
        {
          "id": 925956,
          "author_name": "pranavkasela",
          "author_url": "",
          "post_date": "07/12/2020 11:54:22",
          "content": "<p>Yes unfortunately splitting is the only way to overcome this limitation.\nThe <code>%env JOBLIB_TEMP_FOLDER=/tmp</code> writes the files generated by the joblib library in the /tmp folder instead of the current working folder, it is useful only if you are using the joblib library or any library you are using uses joblil, for example sklearn.</p>",
          "votes": null,
          "replies": []
        }
      ]
    }
  ],
  "raw_markdown_by_id": {
    "925771": "OSError: [Errno 28] No space left on device\n![](https://www.googleapis.com/download/storage/v1/b/kaggle-user-content/o/inbox%2F3004733%2F95a669426afa3d55431e3c1f64926477%2FScreenshot%202020-07-12%20at%202.30.01%20PM.png?generation=1594544435440970&amp;alt=media)\nMy HDD is getting fulled. How can I resolve this\n( I am new to kaggle) \n\nI found a solution\n`%env JOBLIB_TEMP_FOLDER=/tmp\n`\nbut I don't know what does it mean. Help!",
    "925862": "It is difficult to understand what is causing this problem without having a look at the actual code. You can share the notebook for analysis. However, You can check whether you are writing some file here or saving the processed image here. \n\nYou can check the contents of the output directory.",
    "925882": "I was splitting the data and making new files of that and HDD(hard drive) of kaggle is filled as new memory is filling. Kaggle HDD limit is 5GB (as you can see in the image).\nNow I am thinking to do in parts and combining them.",
    "925956": "Yes unfortunately splitting is the only way to overcome this limitation.\nThe ` %env JOBLIB_TEMP_FOLDER=/tmp ` writes the files generated by the joblib library in the /tmp folder instead of the current working folder, it is useful only if you are using the joblib library or any library you are using uses joblil, for example sklearn."
  },
  "source": "meta"
}