Hi,
is there any way to set/change the label after the filesystem has been created?
Best regards,
Felix
--
To unsubscribe from this list: send the line unsubscribe linux-btrfs in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Add kmalloc_nofail(), kcalloc_nofail(), and kzalloc_nofail(). These
functions are equivalent to kmalloc(), kcalloc(), and kzalloc(),
respectively, except that they will never return NULL and instead loop
forever trying to allocate memory.
If the first allocation attempt fails, a warning will be
Add set_extent_dirty_nofail(). This function is equivalent to
set_extent_dirty(), except that it will never fail because of allocation
failure and instead loop forever trying to allocate memory.
If the first allocation attempt fails, a warning will be emitted,
including a call trace. Subsequent
On Tue, 2010-08-24 at 03:50 -0700, David Rientjes wrote:
These were added as helper functions for documentation and auditability.
No future callers should be added.
git grep GFP_NOFAIL isn't auditable enough?
might as well declare these functions depricated if you really want to
do this.
FWIW
On Tue, 2010-08-24 at 03:50 -0700, David Rientjes wrote:
Add set_extent_dirty_nofail(). This function is equivalent to
set_extent_dirty(), except that it will never fail because of allocation
failure and instead loop forever trying to allocate memory.
If the first allocation attempt fails,
On 2010-08-24 15:29, Peter Zijlstra wrote:
On Tue, 2010-08-24 at 03:50 -0700, David Rientjes wrote:
These were added as helper functions for documentation and auditability.
No future callers should be added.
git grep GFP_NOFAIL isn't auditable enough?
might as well declare these functions
On Tue, Aug 24, 2010 at 03:29:18PM +0200, Peter Zijlstra wrote:
On Tue, 2010-08-24 at 03:50 -0700, David Rientjes wrote:
These were added as helper functions for documentation and auditability.
No future callers should be added.
git grep GFP_NOFAIL isn't auditable enough?
might as well
* dan.magenhei...@oracle.com dan.magenhei...@oracle.com [2010-08-20 08:14:59]:
Hi Christophe (and others interested in cleancache progress) --
Thanks for taking some time to talk with me about cleancache
at LSF summit! You had some interesting thoughts and suggestions
that I said I would
On Tuesday, 24 August, 2010, Felix Blanke wrote:
Hi,
is there any way to set/change the label after the filesystem has been
created?
There was a patch to do that. But AFAICT this patch was never merged.
If you are interested look at
[Repost] btrfslabel - kernel space
On Tue, 24 Aug 2010, Jens Axboe wrote:
Should be possible to warn at build time for anyone using __GFP_NOFAIL
without wrapping it in a function.
We could make this __deprecated functions as Peter suggested if you think
build time warnings for existing users would be helpful.
--
To
On Tue, 24 Aug 2010, Dave Chinner wrote:
git grep GFP_NOFAIL isn't auditable enough?
might as well declare these functions depricated if you really want to
do this.
Also, if you are going to add tight loops, you might want to put a
backoff in the loops like
On Tuesday, 24 August, 2010, you (Felix Blanke) wrote:
Hi,
thanks for your reply.
You mentioned that it should be possible to change the label of an
unmounted
filesystem, but you didn't mentioned how. :( I can't find a command that
does that.
True, I have to admit that my reply was not
Hi,
ah ok :) I thought there is a way without the patch to change the label of
unmounted
fs.
I am interested! If it is not to mutch work for you it would be great to have
that
feature.
It's kind of strange that it is not possible to do that with the default btrfs
utilities, because it's such
13 matches
Mail list logo
