From: Jim <jim@webstarts.com>
To: Hugo Mills <hugo@carfax.org.uk>,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: delete disk proceedure
Date: Tue, 05 Jun 2012 12:05:07 -0400 [thread overview]
Message-ID: <4FCE2E33.6090209@webstarts.com> (raw)
In-Reply-To: <20120605160019.GI15986@carfax.org.uk>
[resent after getting rid of the damn signature]
Sorry I missed the list last time, I hit reply too fast. Yes, this
sounds like a good idea. I will try it and let you know.
Jim Maloney
On 06/05/2012 12:00 PM, Hugo Mills wrote:
> [Please keep replies on the list]
>
> On Tue, Jun 05, 2012 at 11:53:20AM -0400, Jim wrote:
>> Thanks for the response. When I say mounts don't work I mean that
>> when I try to mount an exported directory on an older os (most of my
>> machines are centos 5.7) with a non btrfs kernel I get an "unknown
>> filesystem" error. If we can get around this I would be very happy.
> On my NFS exports, I found that I have to set the fsid to something
> unique for each subvolume I export. In my case, this prevents all of
> the exported filesystems being the same, but it might also help with
> your problem.
>
> /media/video *(ro,async,fsid=0x13570,no_subtree_check)
>
> Hugo.
>
>> On 06/05/2012 11:47 AM, Hugo Mills wrote:
>>> On Tue, Jun 05, 2012 at 10:38:11AM -0400, Jim wrote:
>>>> Good morning btrfs list,
>>>> I had written about 2 weeks ago about using extra btrfs space in an
>>>> nfs file system setup. Nfs seems to export the files but the mounts
>>>> don't work on older machines without btrfs kernels.
>>> "The mounts don't work" -- can you be more specific here?
>>>
>>> It would seem that if we can get to the bottom of that problem, you
>>> won't have to muck around with your current set-up at all.
>>>
>>> Hugo.
>>>
-
next prev parent reply other threads:[~2012-06-05 16:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 14:38 delete disk proceedure Jim
2012-06-05 15:47 ` Hugo Mills
[not found] ` <4FCE2B70.9020107@webstarts.com>
2012-06-05 16:00 ` Hugo Mills
2012-06-05 16:05 ` Jim [this message]
2012-06-05 16:19 ` Helmut Hullen
2012-06-05 17:04 ` Hugo Mills
2012-06-05 17:12 ` Jim
2012-06-05 17:18 ` Hugo Mills
2012-06-05 17:23 ` Helmut Hullen
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=4FCE2E33.6090209@webstarts.com \
--to=jim@webstarts.com \
--cc=hugo@carfax.org.uk \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.