'fsresize' is your friend after you change your partition sizes.
On Mon, Nov 5, 2018, 5:12 PM Chuck Hast Select morsels of good data, thanks to you all. I went in and looked at the
> 9.1G partition,
> it has /tmp and /var in there so yes those have a bunch of log files and
> whatnot in there.
>
Select morsels of good data, thanks to you all. I went in and looked at the
9.1G partition,
it has /tmp and /var in there so yes those have a bunch of log files and
whatnot in there.
Now I will just re-size the thing when I get home (I am on the road in a
hotel tonight). I am
going to have to
On Mon, 5 Nov 2018, Nat Taylor wrote:
if you type
du / | sort -n
And, if you append the -sh options to the disk usage command the results
will be a summary for each section (e.g., directory) and in human-readable
format.
A second pass within a large directory, without the '-s' option
if you type
du / | sort -n
it will tell you the size of all the files and folders underneath /
(Everything!), and pipe it to the sort program, which will sort by size
when you give it the -n flag
you will need to wait a while for the operation to complete, and it won't
look into protected
On 11/4/18 8:37 PM, Chuck Hast wrote:
> Well, doing a df I see that / is the 9.1G partition and the other one is
> /home.
>
> Prior to cleaning, the partition was 9.05G full, after doing the cleanup it
> is now down to 8.7G.
> so I have got to see what all is in it. Or I will have to make it
Well, doing a df I see that / is the 9.1G partition and the other one is
/home.
Prior to cleaning, the partition was 9.05G full, after doing the cleanup it
is now down to 8.7G.
so I have got to see what all is in it. Or I will have to make it bigger. I
have a boat load of empty
space on the HD so
Use 'df' to see what partitions are in use and percentage.
On Sun, Nov 4, 2018, 8:14 PM Bill Barry On Mon, Nov 5, 2018 at 3:40 AM Chuck Hast wrote:
>
> > I went in and was able to boot to the previous image. The recovery
> offered
> > to remove all
> > unneeded files, then did the update. I was
On Mon, Nov 5, 2018 at 3:40 AM Chuck Hast wrote:
> I went in and was able to boot to the previous image. The recovery offered
> to remove all
> unneeded files, then did the update. I was able to restart it. For
> some reason it reported
> that root was full, but (I double checked this) it was
I went in and was able to boot to the previous image. The recovery offered
to remove all
unneeded files, then did the update. I was able to restart it. For
some reason it reported
that root was full, but (I double checked this) it was saying "root". There
is a "root " directory
in the boot
cd /
du . | sort -n
On Sun, Nov 4, 2018 at 5:42 PM Bill Barry wrote:
> On Mon, Nov 5, 2018 at 1:34 AM Chuck Hast wrote:
>
> > Folks.
> > I went to do an update when it tried to upgrade things the whole thing
> > abended
> > with a batch of lines indicating that "root was almost full". I went
On Mon, Nov 5, 2018 at 1:34 AM Chuck Hast wrote:
> Folks.
> I went to do an update when it tried to upgrade things the whole thing
> abended
> with a batch of lines indicating that "root was almost full". I went to
> look at it and
> found the the directory had to be accessed as administrator,
Folks.
I went to do an update when it tried to upgrade things the whole thing
abended
with a batch of lines indicating that "root was almost full". I went to
look at it and
found the the directory had to be accessed as administrator, when I looked
into it
I did not see anything of large size. The
12 matches
Mail list logo
