On Tue, Apr 15, 2014 at 08:47:27PM +0100, Filipe David Borba Manana wrote:
Because the function open_file_or_dir() always opened the input file in
read/write mode (O_RDWR), we were not able to due a compression property
get against a file living in a read-only subvolume/snapshot.
Fix this by
+subvol = argv[optind+1];
+dst = argv[optind+2];
+struct btrfs_ioctl_vol_args_v2 args;
Does the standard C allow to define a variable in the middle in a
function instead of in the begin ?
Anyway, even not required, I suggest to fill args by zero.
+ memset(args, 0,
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp philipp.andr...@gmail.com
---
btrfs_cmds.c | 48
1 files changed, 40 insertions(+), 8
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp philipp.andr...@gmail.com
---
btrfs_cmds.c | 44
1 files changed, 36 insertions(+), 8
Hi Andreas,
On 04/25/2011 03:47 PM, Andreas Philipp wrote:
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp philipp.andr...@gmail.com
---
btrfs_cmds.c | 44
Excerpts from Goffredo Baroncelli's message of 2011-04-25 17:34:46 -0400:
Hi Andreas,
On 04/25/2011 03:47 PM, Andreas Philipp wrote:
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp
Andreas Philipp wrote:
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp philipp.andr...@gmail.com
---
btrfs_cmds.c | 44
1 files changed,
+ while(1) {
+ int c = getopt(argc, argv, r);
+ if (c 0)
+ break;
+ switch(c) {
+ case 'r':
+ optind++;
+ readonly = 1;
+
Use BTRFS_IOC_CREATE_SNAP_V2 instead of BTRFS_IOC_CREATE_SNAP and add
an option for the creation of a readonly snapshot.
Signed-off-by: Andreas Philipp philipp.andr...@gmail.com
---
btrfs_cmds.c | 44
1 files changed, 36 insertions(+), 8
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
IMHO, this is related to how the debug options of the kernel are
configured. Attached you find two config files, both for kernel
version 2.6.38, with the one named 2.6.38-debug everything works and
with the other one newly created subvolumes are read only.
I've figured out what's wrong.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
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
On Wed, Mar 23, 2011 at 3:21 PM, Andreas Philipp
philipp.andr...@gmail.com wrote:
I think it is since I upgraded to kernel version 2.6.38 (I
do not create subvolumes on a regular basis.).
thor btrfs # btrfs subvolume create 123456789
Create subvolume './123456789'
thor btrfs # touch
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.03.2011 10:25, Li Zefan wrote:
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 23.03.2011 11:07, Andreas Philipp wrote:
On 23.03.2011 10:25, Li Zefan wrote:
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
16 matches
Mail list logo