Received: by oss.sgi.com id ; Mon, 2 Oct 2000 11:58:52 -0700 Received: from deliverator.sgi.com ([204.94.214.10]:18210 "EHLO deliverator.sgi.com") by oss.sgi.com with ESMTP id ; Mon, 2 Oct 2000 11:58:34 -0700 Received: from nodin.corp.sgi.com (fddi-nodin.corp.sgi.com [198.29.75.193]) by deliverator.sgi.com (980309.SGI.8.8.8-aspam-6.2/980310.SGI-aspam) via ESMTP id LAA16337; Mon, 2 Oct 2000 11:50:10 -0700 (PDT) mail_from (nobody@info.engr.sgi.com) Received: from info.engr.sgi.com (info.engr.sgi.com [192.26.80.216]) by nodin.corp.sgi.com (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id LAA63005; Mon, 2 Oct 2000 11:57:23 -0700 (PDT) Received: (from nobody@localhost) by info.engr.sgi.com (SGI-8.9.3/8.9.3) id LAA26671; Mon, 2 Oct 2000 11:56:05 -0700 (PDT) Date: Mon, 2 Oct 2000 11:56:05 -0700 (PDT) Message-Id: <200010021856.LAA26671@info.engr.sgi.com> X-Pv-Incident: 797165 webPV: jen.americas.sgi.com webExec: webpvupdate,pvincident Reply-To: sgi.bugs.xfs@fido.engr.sgi.com From: pv@relay.sgi.com (lord@sgi.com) Subject: ADD 797165 - rationalise uuid kernel code for XFS To: dxm@engr.sgi.com Cc: linux-xfs@oss.sgi.com Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Return-Path: X-Orcpt: rfc822;linux-xfs-outgoing View Incident: http://co-op.engr.sgi.com/BugWorks/code/bwxquery.cgi?search=Search&wlong=1&view_type=Bug&wi=797165 Status : open Priority : 4 Assigned Engineer : dxm Submitter : nathans *Modified User : lord *Modified User Domain : sgi.com *Description : stick this in a bug so it isn't forgotten... On Jul 21, 8:40am, Nathan Scott wrote: > Subject: Re: LVM vs. kiobuf I/O > > > - Kernel uuid generation support > > ... > ... > > I think there's a bunch of stuff which can be rationalised > there too... ..... ========================== ADDITIONAL INFORMATION (ADD) From: lord@sgi.com (BugWorks) Date: Oct 02 2000 11:56:05AM ========================== I was wrong last time. Glen added code to print uuid code from xfs_db, not change it. So we have two conflicing tasks here: 1. turning an existing filesystem into two distinct filesystems. because of how they are created - they would be different devices, but have the same uuid. 2. prevent mounts of the same device when it has multiple paths I think we can make one work automatically and the other require some operator intervention.