From: "l.a walsh" <xfs@tlinx.org>
To: "'Nathan Scott'" <nathans@sgi.com>,
   "'Chris Croswhite'" <ccroswhite@get2chip.com>
Cc: <linux-xfs@oss.sgi.com>
Subject: RE: dd of xfs partition does not mount
Date: Mon, 7 Apr 2003 17:43:10 -0700
Message-ID: <001301c2fd67$d7b64260$1403a8c0@sc.tlinx.org>
Importance: Normal
In-Reply-To: <20030404021852.GF911@frodo>
Sender: linux-xfs-bounce@oss.sgi.com
Errors-to: linux-xfs-bounce@oss.sgi.com
Precedence: bulk
Content-Length: 1230
Lines: 29

	It'd be really beneficial/user-friendly if some message could be
issued in mount about this other that 'generic failure happened'.
I've been bitten by this twice, finally remembering the UUID the
2nd time around -- it's not something most ext2 users are going to be
used to, or ISOFS, or many other file systems.

	Even though a generic status is returned to mount, isn't it possible to
still spit something out on stderr to the effect of 'attempt to mount
duplicate UUID', or does 'mount' redirect stderr as well?  Maybe /dev/tty
would work for interactive terminals and /dev/console otherwise...?

	It's just easy to forget when one does a bunch of iso or FAT
copies...and months (and 20-30 other fs copies later), copy another xfs
fs, and womp...why didn't that work?  If you're lucky, it's not your
first time and you remember (eventually)...otherwise, it can be a bit
crazy-making....

-l


> -----Original Message-----
> From: linux-xfs-bounce@oss.sgi.com
> [mailto:linux-xfs-bounce@oss.sgi.com] On Behalf Of Nathan Scott
> You probably need to use the "nouuid" mount option, or use
> xfs_admin(8) to change the UUID on the copied filesystem.
> You syslog will have more information on the nature of the
> mount failure.