this post was submitted on 12 Feb 2026
13 points (93.3% liked)

Linux

17186 readers
164 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 2 years ago
MODERATORS
MigratingtoLemmy@lemmy.world
13
/var/xorg.log file got HUGEE (sh.itjust.works)
submitted 2 months ago by bridgeenjoyer@sh.itjust.works to c/linux@lemmy.world
8 comments fedilink hide all child comments
 

The other day my PC randomly threw an error saying my hard drive was full. I quickly deleted some games so it wouldn't freeze and then went to look wtf happened to see the xorg.log file was over 200 gigs!! I deleted it and rebooted and was fine.

But what in the world would cause this??

All AMD system, Linux mint.

top 8 comments
sorted by: hot top controversial new old
[–] gens@programming.dev 12 points 2 months ago (2 children)

It could be anything. A good start is to look at... the log.

[–] Lonewolfmcquade@lemmy.world 3 points 2 months ago (2 children)

A lot of us noobs haven't learned how to do this yet. It is unfortunately, not part of most distros Intro guide

[–] frongt@lemmy.zip 6 points 2 months ago

Haven't learned how to... open a file?

[–] gens@programming.dev 3 points 2 months ago* (last edited 2 months ago)

Sometimes the log can be, let's say less useful. Then I'd check the monitor cable. And if the log starts growing after suspend-resume, as that can be buggy.

dmesg (as root or using sudo) prints out all kernel messages since boot, and can also be useful. Xorg errors are usually hardware or driver problems.

Also if you messed with bios... Like the pcie settings.

[–] bridgeenjoyer@sh.itjust.works 1 points 2 months ago

Unfortunately its deleted now, and i wouldn't understand what I'm looking at

[–] vk6flab@lemmy.radio 7 points 2 months ago

What was in the log?

[–] just_another_person@lemmy.world 3 points 2 months ago

You probably have debug logging enabled somewhere.

[–] derbolle@lemmy.world 2 points 2 months ago

if this happens again it's probably a good idea to check the logs.

also try logrotate

be mindful though tgat logging if not configured right can put a lot of wear on your SSD, so it might be an idea to set logrotate to Something rather small and mount your log directory (if you generally don't need logs to survive a reboot) to a tmpfs Mount(if you've got some RAM to spare)