From: Jack <ostroffjh@users.sourceforge.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Approx monthly hard lockups
Date: Thu, 13 May 2021 23:06:02 -0600 [thread overview]
Message-ID: <188d58ad-fc69-e017-dc3b-eec2aa17570e@users.sourceforge.net> (raw)
In-Reply-To: <YJ4EP2LCCRi1qrAE@waltdnes.org>
On 5/13/21 11:01 PM, Walter Dnes wrote:
> On Thu, May 13, 2021 at 06:10:08AM -0700, Mark Knecht wrote
>> Do double check that you log into a directory that doesn't run out of space
>> once a month. That could cause problems also.
> After the "separate /usr" brouhaha, I gave up and went to one file
> system. We all back up our PC's regularly, don't we? <G> "fdisk -l"
> shows my "1 terabyte" drive as...
>
> Device Start End Sectors Size Type
> /dev/sda1 2048 1929381887 1929379840 920G Linux filesystem
> /dev/sda2 1929381888 1953525134 24143247 11.5G Linux swap
>
> I am *NOT* running out of disk space. mc (Midnight Commander) shows
> 617 of 905 gigabytes free when logged in as regular user. 663 of 905
> free when logged in as root. Soon to be several gigabytes more free
> space when I do some cleaning up of obsolete unused cruft accumulated
> over the years.
One thing I've done in a similar situation is to boot to a live image.
That way, the current system does not mess with anything in /var/log and
you might find something which would be overwritten by a fresh boot.
next prev parent reply other threads:[~2021-05-14 5:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-12 16:35 [gentoo-user] Approx monthly hard lockups Walter Dnes
2021-05-12 18:16 ` Mark Knecht
2021-05-13 2:44 ` Walter Dnes
2021-05-13 2:50 ` Dale
2021-05-13 2:57 ` Mark Knecht
2021-05-13 7:19 ` Walter Dnes
2021-05-13 13:10 ` Mark Knecht
2021-05-14 5:01 ` Walter Dnes
2021-05-14 5:06 ` Jack [this message]
2021-05-13 15:42 ` Neil Bothwick
2021-05-13 5:21 ` Andreas Fink
2021-05-12 21:40 ` Jack
2021-05-13 2:49 ` Walter Dnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=188d58ad-fc69-e017-dc3b-eec2aa17570e@users.sourceforge.net \
--to=ostroffjh@users.sourceforge.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox