From: Andreas Dilger <adilger@turbolinux.com>
To: Dave Kleikamp <shaggy@austin.ibm.com>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Alexander Viro <viro@math.psu.edu>,
Linux kernel development list <linux-kernel@vger.kernel.org>,
Linux FS development list <linux-fsdevel@vger.kernel.org>
Subject: Re: (struct dentry *)->vfsmnt;
Date: Wed, 14 Mar 2001 14:07:37 -0700 (MST) [thread overview]
Message-ID: <200103142107.f2EL7ba10641@webber.adilger.int> (raw)
In-Reply-To: <3AAFCD2E.59A3A809@austin.ibm.com> from Dave Kleikamp at "Mar 14, 2001 01:57:34 pm"
David Kleikamp writes:
> Let me start with a disclaimer stating that it's been a few years since
> I've worked with AIX, but this is what I believe happens.
>
> mount itself doesn't do anything except read /etc/filesytems (AIX's
> version of /etc/fstab). LVM maintains the information primarily in the
> ODM (yuck). The utilities such as mkfs, mklv, chfs, etc. modify this
> information in the ODM. The exportvg command extracts the information
> from the ODM (and /etc/filesystems?) and stores it somewhere in the
> volume group. Only then can the volume group be imported by another
> system with the importvg command, which then populates the ODM and
> /etc/filesystems.
Actually, I'm pretty sure you _never_ need to exportvg in order to have
it work on another system. That's one of the great things about AIX LVM,
because it means you can move a VG to another system after a hardware
problem, and not have any problems importing it (journaled fs also helps).
AFAIK, the only think exportvg does is remove VG information from the
ODM and /etc/filesystems.
I suppose it is possible that because AIX is so tied into the ODM and
SMIT, that it updates the VGDA mountpoint info whenever a filesystem
mountpoint is changed, but this will _never_ work on Linux because of
different tools versions, distributions, etc. Also, it would mean on
AIX that anyone editing /etc/filesystems might have a broken system at
vgimport time (wouldn't be the first time that not using ODM/SMIT caused
such a problem).
> ... I do think that the LVM is a reasonable place to store this kind of
> information.
Yes, even though it would tie the user into using a specific version of
mount(), I suppose it is a better solution than storing it inside the
filesystem. It will work with non-ext2 filesystems, and it also allows
you to store more information than simply the mountpoint (e.g. mount
options, dump + fsck info, etc). In the end, I will probably just
save the whole /etc/fstab line into the LV header somewhere, and extract
it at importvg time (possibly with modifications for vgname and mountpoint).
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
next prev parent reply other threads:[~2001-03-14 21:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-09 23:20 (struct dentry *)->vfsmnt; LA Walsh
2001-03-10 1:00 ` Alexander Viro
2001-03-10 1:56 ` LA Walsh
2001-03-10 2:42 ` Alexander Viro
2001-03-14 1:28 ` Andreas Dilger
2001-03-14 2:32 ` Alexander Viro
2001-03-14 4:27 ` Andreas Dilger
2001-03-14 5:11 ` Alexander Viro
2001-03-14 5:19 ` Andreas Dilger
2001-03-14 5:49 ` Alexander Viro
2001-03-14 6:05 ` Andreas Dilger
2001-03-14 6:50 ` Alexander Viro
2001-03-14 17:26 ` Andreas Dilger
2001-03-14 17:40 ` Matthew Wilcox
2001-03-14 18:06 ` Andreas Dilger
2001-03-14 18:11 ` Alexander Viro
2001-03-14 19:14 ` Andreas Dilger
2001-03-14 19:32 ` Alexander Viro
2001-03-14 20:21 ` Ragnar Kjørstad
2001-03-14 19:31 ` Dave Kleikamp
2001-03-14 19:45 ` Andreas Dilger
2001-03-14 19:51 ` Alexander Viro
2001-03-14 19:57 ` Dave Kleikamp
2001-03-14 21:07 ` Andreas Dilger [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-03-15 12:21 bsuparna
2001-03-15 12:59 bsuparna
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200103142107.f2EL7ba10641@webber.adilger.int \
--to=adilger@turbolinux.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@austin.ibm.com \
--cc=viro@math.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox