On Apr 22, 2008 18:08 -0600, Chris Worley wrote:
The error specifically complains about the first OST/disk on the new
OSS, OST0026. It's tunefs.lustre output was:
On the OSS in question, for each OST, I did:
# tunefs.lustre --writeconf --ost
--mgsnode=[EMAIL PROTECTED],[EMAIL
Never mind the last question... the device in step #3 is the MDT.
On Wed, Apr 23, 2008 at 9:51 AM, Chris Worley [EMAIL PROTECTED] wrote:
On Wed, Apr 23, 2008 at 8:50 AM, D. Marc Stearman [EMAIL PROTECTED] wrote:
3. Re-run a write-conf on your MGS node. Something like this:
Sorry to require remedial instructions... it works now. The trick was
my misunderstanding that the tunefs.lustre needed to be run on the MGS
given the mdt.
I've rerun tunefs on the new OSS for all the OST's w/ the original
settings, and. likewise on the MGS for the MDT, with all original
Does anybody have any clues, or do I need to rebuild the entire FS from scratch?
On Mon, Apr 21, 2008 at 9:31 PM, Chris Worley [EMAIL PROTECTED] wrote:
On Mon, Apr 21, 2008 at 9:22 PM, Chris Worley [EMAIL PROTECTED] wrote:
The only configuration error on my OSS was: I initially only had
On Tue, Apr 22, 2008 at 2:21 PM, Cliff White [EMAIL PROTECTED] wrote:
Chris Worley wrote:
Does anybody have any clues, or do I need to rebuild the entire FS from
scratch?
First, what is in your client modprobe.conf? Should only be 'tcp' for
tcp-only clients.
It is/was:
The only configuration error on my OSS was: I initially only had
o2ib0(ib0) in my modprobe.conf. After unmounting all the OSTs, and
getting the modprobe.conf right:
options lnet networks=o2ib0(ib0),tcp0(eth0)
...and remounting from scratch, both ksocklnd and ko2iblnd are now
loaded properly.
