Skip to content
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

'du' reports "Circular directory structure." #11514

Closed
1 of 2 tasks
KarlCHansen opened this issue Apr 25, 2024 · 5 comments
Closed
1 of 2 tasks

'du' reports "Circular directory structure." #11514

KarlCHansen opened this issue Apr 25, 2024 · 5 comments

Comments

@KarlCHansen
Copy link

KarlCHansen commented Apr 25, 2024

Windows Version

Microsoft Windows [Version 10.0.19045.4291]

WSL Version

2.1.5.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.146.1-2

Distro Version

Ubuntu 22.04

Other Software

After installing Code Composer Studio for Linux, I ran du -k / | sort -n to check how much disk space was being used. The du command spits out the warning about Circular directory structure:

# du -k / | sort -n
du: WARNING: Circular directory structure.
This almost certainly means that you have a corrupted file system.
NOTIFY YOUR SYSTEM MANAGER.
The following directory is part of the cycle:
/sys/kernel/debug/device_component

Repro Steps

  1. Install Ubuntu 22.04 in WSL.
  2. Open a bash window.
  3. Enter root mode via sudo bash.
  4. Install latest updates via apt update && apt upgrade.
  5. Run du -k / | sort -n.
  6. Very quickly, du spits out the above warning message.

Expected Behavior

No warning, no circular directory structure messages.

Actual Behavior

Command du spits out warning about circular directory structure.

Diagnostic Logs

No response

Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The scipt will output the path of the log file once done.

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to wsl-gh-logs@microsoft.com with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@KarlCHansen
Copy link
Author

I am collecting the logs, although they will reveal nothing special.

Regarding the two similar issues -- #389 says closed/fixed, but it happens in latest WSL/Ubuntu 22.04. #7349 says closed due to inactivity, but it is definitely a problem.

@KarlCHansen
Copy link
Author

Copy link

The log file doesn't contain any WSL traces. Please make sure that you reproduced the issue while the log collection was running.

Diagnostic information
.wslconfig found
Detected appx version: 2.1.5.0
Found no WSL traces in the logs

Copy link
Contributor

This issue has been automatically closed since it has not had any author activity for the past 7 days. If you're still experiencing this issue please re-file it as a new issue.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant