All of lore.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Andreas Philipp <philipp.andreas@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: read-only subvolumes?
Date: Wed, 23 Mar 2011 17:25:28 +0800	[thread overview]
Message-ID: <4D89BC88.5030406@cn.fujitsu.com> (raw)
In-Reply-To: <4D89ADA7.2000803@gmail.com>

> Hi all,
> 
> When I am creating subvolumes I get this strange behavior. If I create
> a subvolume with a name longer than 4 characters it is read-only, if
> the name is shorter than 5 characters the subvolume is writeable as
> expected. I think it is since I upgraded to kernel version 2.6.38 (I
> do not create subvolumes on a regular basis.). I will compile one of
> the latest 2.6.37 kernels to see whether there the problem exists,
> too. Another interesting point is that previously created subvolumes
> are not affected.
> 
> Thanks,
> Andreas Philipp
> 
> thor btrfs # btrfs subvolume create 123456789
> Create subvolume './123456789'
> thor btrfs # touch 123456789/lsdkfj
> touch: cannot touch `123456789/lsdkfj': Read-only file system

This is really odd, but I can't reproduce it.

I created a btrfs filesystem on 2.6.37 kernel, and rebooted to latest
2.6.38+, and tried the procedures as you did, but nothing bad happend.

  parent reply	other threads:[~2011-03-23  9:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-23  8:21 read-only subvolumes? Andreas Philipp
2011-03-23  9:01 ` Fajar A. Nugraha
2011-03-23  9:25 ` Li Zefan [this message]
2011-03-23 10:07   ` Andreas Philipp
2011-03-23 10:14     ` Andreas Philipp
     [not found]       ` <4D89CBF4.6040600@gmail.com>
2011-03-24  6:30         ` Li Zefan
2011-03-24  9:31         ` Li Zefan

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=4D89BC88.5030406@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=philipp.andreas@gmail.com \
    /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.