[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[NOAAPORT #FHN-627883]: mistral home file system full
- Subject: [NOAAPORT #FHN-627883]: mistral home file system full
- Date: Tue, 29 Sep 2020 13:12:06 -0600
Hi Yixin,
Here is the reply from the lead Unidata system administrator on the question
of how we are upgrading our systems from CentOS 6 to 8:
"I do not have an image in terms that most people expect, that is a
VM or .vmdk image. I have a disk image that I either dd or replicate
via linux mdadm.
I think it's a good generic base, but may include extraneous capabilities
other sites don't need or may ever use, like the capabilities to configure
RAID 1's on the fly. I've bypassed the conventional CentOS 8.x default
wisdom in several areas including avoiding UEFI booting, XFS, system
defined network device naming (must have eth0), ... so I've twisted it much
more to our liking
With that said, I'm willing to share it and help get it going at LSU..."
Given the above, I am not sure that this is the easiest/best way for you
to upgrade, for instance, mistral.
Just so you know, my upgrade from CentOS 6 to CentOS 8 for my VMware
VM was done by downloading a pre-configured image from a site, and then
configuring it to have all of the packages I needed for my development
efforts. This is not the typical way for bare metal installs, but I
thought I'd throw in my experience anyway.
Cheers,
Tom
--
****************************************************************************
Unidata User Support UCAR Unidata Program
(303) 497-8642 P.O. Box 3000
address@hidden Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: FHN-627883
Department: Support NOAAPORT
Priority: High
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata
inquiry tracking system and then made publicly available through the web. If
you do not want to have your interactions made available in this way, you must
let us know in each email you send to us.