Configuring default mount options..
If using BTRFS on a removable drive... it may be a problem for example, to always mount with compression, or always mount with encryption (If supported in future)... perhaps btrfstune could define default mount options, such as compression... so if there is a BTRFS filesystem on a removable hard drive, or flash stick, the filesystem can be configured to mount with compression by default.
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is used under those circumstances.
A. James Lewis
Quoted 1 line · A. James Lewis
If using BTRFS on a removable drive... it may be a problem for exampl=
e,
Quoted 3 lines
to always mount with compression, or always mount with encryption (If supported in future)... perhaps btrfstune could define default mount options, such as compression... so if there is a BTRFS filesystem on =
a
Quoted 1 line
removable hard drive, or flash stick, the filesystem can be configure=
d
Quoted 6 lines
to mount with compression by default.
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is used under those circumstances.
Quoted 6 lines
A. James Lewis
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs=
" in
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info.ht=
ml
Quoted 1 line
That's actually a good idea. Perhaps an override flag could be specified in case you do not wish to use said default mount options?
Regards,
Sebastian J.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 16 lines · Sebastian 'gonX' Jensen
Quoted 15 lines · A. James Lewis
If using BTRFS on a removable drive... it may be a problem for example, to always mount with compression, or always mount with encryption (If supported in future)... perhaps btrfstune could define default mount options, such as compression... so if there is a BTRFS filesystem on a removable hard drive, or flash stick, the filesystem can be configured to mount with compression by default.
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is used under those circumstances.
A. James Lewis
Quoted 9 lines
Quoted 5 lines
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.htmlThat's actually a good idea. Perhaps an override flag could be specified in case you do not wish to use said default mount options?
Indeed, if any mount options are specified they would override defaults... but if you plug in a removable drive, you there's no way to specify mount options, but it's quite likley that you would want some, like compression for example.
Quoted 2 lines
Regards,
Sebastian J.
Quoted 3 lines · A. James Lewis
Quoted 2 lines · Sebastian 'gonX' Jensen
Quoted 1 line · A. James Lewis
If using BTRFS on a removable drive... it may be a problem for exa=
mple,
Quoted 1 line
Quoted 1 line
Quoted 1 line
to always mount with compression, or always mount with encryption =
(If
Quoted 1 line
Quoted 1 line
Quoted 1 line
supported in future)... perhaps btrfstune could define default mou=
nt
Quoted 1 line
Quoted 1 line
Quoted 1 line
options, such as compression... so if there is a BTRFS filesystem =
on a
Quoted 1 line
Quoted 1 line
Quoted 1 line
removable hard drive, or flash stick, the filesystem can be config=
ured
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
to mount with compression by default.
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is use=
d
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
under those circumstances.
A. James Lewis
--
To unsubscribe from this list: send the line "unsubscribe linux-bt=
rfs" in
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
the body of a message to [email protected]
More majordomo info at =C2=A0http://vger.kernel.org/majordomo-info=
=2Ehtml
Quoted 7 lines
Quoted 5 lines
Quoted 1 line
That's actually a good idea. Perhaps an override flag could be specified in case you do not wish to use said default mount options?
Indeed, if any mount options are specified they would override defaults... but if you plug in a removable drive, you there's no way =
to
Quoted 1 line
specify mount options, but it's quite likley that you would want some=
,
Quoted 8 lines
like compression for example.
Quoted 2 lines
Regards,
Sebastian J.
Oh, you're talking about udisks/HAL automount feature I assume. It should be possible to specify mount parameters in some way for those implementations, but that isn't really a "fix" if you're using multiple computers - a per-drive mount parameter stored somewhere on the drive wouldn't be that bad to save some time.
Regards,
Sebastian J.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 8 lines
=20
From: Oystein Viggen <oysteivi <at> tihlde.org>
Subject: Re: Configuring default mount options..
Newsgroups: gmane.comp.file-systems.btrfs
Date: 2010-07-26 06:08:54 GMT (5 hours and 4 minutes ago) =20
* ["A. James Lewis"]=20
=20
Quoted 8 lines
Quoted 3 lines
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is used under those circumstances.
=20
There has been talk of supporting per-file (and I assume recursive per-directory default) attributes for raid level. Things like encryption and compression could fit well into such a scheme. =20
That's a nice solution, particularly for encryption... especially once = the GUI file managers are able to indicate the settings.... It would se= em to be necessary to allow these parameters to be set in the root, but=
otherwise nice.
I'm not sure if it negates the value of having default "preferences" st= ored somwhere... certainly it would take longer to implement, but maybe=
the default parameters for all these settings are simply equivalent to= whatever is defined in the root of each filesystem... so really one so=
lution can be a subset of the other.
Quoted 8 lines
=20
I don't believe the code for this is written yet, however. =20
=C3=98ystein
--=20
ssh -c rot13 otherhost
=20
=20
A. James Lewis
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
* ["A. James Lewis"]=20
Quoted 3 lines
Maybe there is a way to do this already, but it seems like the filesystem itself should contain preferences for the way it is used under those circumstances.
There has been talk of supporting per-file (and I assume recursive per-directory default) attributes for raid level. Things like encryption and compression could fit well into such a scheme.
I don't believe the code for this is written yet, however.
=D8ystein
--=20
ssh -c rot13 otherhost
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html