fs_info, which is allocated in open_ctree(), should be freed
in close_ctree().
Signed-off-by: Li Zefan
---
candidate for stable ?
---
fs/btrfs/disk-io.c |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
index 280de15..199cc26 1006
On Wed, Jul 28, 2010 at 08:31:10AM +0800, Yan, Zheng wrote:
> On Wed, Jul 28, 2010 at 4:30 AM, Dave Cundiff wrote:
> > Hello,
> >
> > I installed the git repo kernel and added some debug to the ENOSPC
> > returns. Unfortunately its still failing. If it helps any its bombing
> > out in btrfs_chec
Allow users to delete the snapshots/subvols they own. Instead of
CAP_SYS_ADMIN, require that
- the user has write and exec permission on the parent directory
- security_inode_rmdir() doesn't object
- the user has write and exec permission on the subvol directory
- the user owns the subvol dir
> From: Andreas Dilger
> Sent: Tuesday, August 03, 2010 12:34 PM
> To: Dan Magenheimer
> Subject: Re: [PATCH V3 0/8] Cleancache: overview
>
> On 2010-08-03, at 11:35, Dan Magenheimer wrote:
> > - The FS should be block-device-based (e.g. a ram-based FS
> > such as tmpfs should not enable cleancac
Hi Michael
This theme was discussed several times in the past.
Short answer: now it is not possible, what you are asking.
Long answer: rearranging the layout of the filesystem, it is easy to do what
are you asking with the current tools. But this changes have to be integrated
in the distributi
On 2010-08-03, at 11:35, Dan Magenheimer wrote:
> - The FS should be block-device-based (e.g. a ram-based FS
> such as tmpfs should not enable cleancache)
When you say "block device based", does this exclude network filesystems? It
would seem cleancache, like fscache, is actually best suited to
Fedora provides yum-fs-snapshot. If installed, on each package
installation or update a snapshot of all btrfs filesystems is taken, so
it is possible to revert the installation/update.
Suppose an update failed and I want to get back: with
# btrfs subvolume set-default yum-snapshot-whatever /
> From: Boaz Harrosh [mailto:bharr...@panasas.com]
> Sent: Tuesday, August 03, 2010 10:23 AM
> To: Dan Magenheimer
> Subject: Re: [PATCH V3 0/8] Cleancache: overview
>
> On 07/24/2010 12:17 AM, Dan Magenheimer wrote:
> >>> On Fri, Jul 23, 2010 at 06:58:03AM -0700, Dan Magenheimer wrote:
> CHR
On 07/24/2010 12:17 AM, Dan Magenheimer wrote:
>>> On Fri, Jul 23, 2010 at 06:58:03AM -0700, Dan Magenheimer wrote:
CHRISTOPH AND ANDREW, if you disagree and your concerns have
not been resolved, please speak up.
>>
>> Hi Christoph --
>>
>> Thanks very much for the quick (instantaneous?)
Here is mine...
btrfs-snap
Description: application/shellscript
Le 03 août 2010 à 15:42, Benjamin Griese a écrit:
> Hello guys,
> I would be interested in that script, maybe in both of yours,
It is not supposedly bulletproof. Use at your own risks.
backup1:/usr/local/bin# crontab -l
# m h dom mon dow command
# hourly backup
0 * * * * /usr/local/bin/snapsho
Hello guys,
I would be interested in that script, maybe in both of yours,
Thank you! :)
On Tue, Aug 3, 2010 at 15:48, Xavier Nicollet wrote:
>
> Le 03 août 2010 à 14:44, birger a écrit:
> > I have a neat snapshot script for my laptop that I wouldn't mind
> > sharing. Works mostly like the NetApp
Le 03 août 2010 à 14:44, birger a écrit:
> I have a neat snapshot script for my laptop that I wouldn't mind
> sharing. Works mostly like the NetApp snapshots. Set up a cron job with
> a prefix for the snapshot name and the number of snapshots to keep. It's
> very easy to set up for schemes like 24
Hi, Adi
On Mon, 02 Aug 2010 21:37:16 +0200, Adi wrote:
now i get that error (on btrfsck):
parent transid verify failed on 5403553792 wanted 103380 found 103378
btrfsck: disk-io.c:739: open_ctree_fd: Assertion `!(!tree_root->node)' failed.
if i want to mount it, it shows the same error in dmesg
My last one for now...
I see from the project ideas list that some of what I want is there
already in the "Incremental backups" section. What is missing is the
ability to create a new subvol at the remote end given an existing
volume with a common subvolume to work from.
Some kind of UUID-like fi
I would like a way to list the creation date of subvolumes. The only
data I find now would be the ID in the output of btrfs subvol list. I
assume it is strictly incremental, so it gives a way to order the
snapshots. Still, I would like to know date/time of creation even when
it is not in the name o
I understand that there is resistance to adding dependencies to the
tools package, so how about a contrib package for contributed tools?
I have a neat snapshot script for my laptop that I wouldn't mind
sharing. Works mostly like the NetApp snapshots. Set up a cron job with
a prefix for the snapsho
On Mon, Aug 02, 2010 at 05:42:00PM +0900, Donggeun Kim wrote:
> In some cases, resizing a file system to the maximum device size is required.
> When flashing a file system image to a block device,
> the file system does not fit into the block device's size.
> Currently, executing 'btrfsctl' applica
18 matches
Mail list logo
