search for: 814e

...0, #85 ; 0x55 8140: cmp lr, ip 8142: bne.n 8168 <foo+0x44> 8144: ldrb.w ip, [r1, #2] 8148: ldrb r3, [r4, #2] 814a: cmp r3, ip 814c: it ne 814e: popne {r4, r6, r7, pc} // a function return 8150: ldrb.w ip, [r1, #1] 8154: ldrb r3, [r4, #1] 8156: cmp r3, ip 8158: bne.n 8168 <foo+0x44> 815a:...

...cmp lr, ip > 8142: bne.n 8168 <foo+0x44> > > 8144: ldrb.w ip, [r1, #2] > 8148: ldrb r3, [r4, #2] > 814a: cmp r3, ip > 814c: it ne > 814e: popne {r4, r6, r7, pc} // a function return > > 8150: ldrb.w ip, [r1, #1] > 8154: ldrb r3, [r4, #1] > 8156: cmp r3, ip > 8158: bne.n 8168 <foo+0x44>...

...0, #85 ; 0x55 8140: cmp lr, ip 8142: bne.n 8168 <foo+0x44> 8144: ldrb.w ip, [r1, #2] 8148: ldrb r3, [r4, #2] 814a: cmp r3, ip 814c: it ne 814e: popne {r4, r6, r7, pc} // a function return 8150: ldrb.w ip, [r1, #1] 8154: ldrb r3, [r4, #1] 8156: cmp r3, ip 8158: bne.n 8168 <foo+0x44> 815a:...

...x44> >> >> >> >> 8144: ldrb.w ip, [r1, #2] >> >> 8148: ldrb r3, [r4, #2] >> >> 814a: cmp r3, ip >> >> 814c: it ne >> >> 814e: popne {r4, r6, r7, pc} // a >> function return >> >> >> >> 8150: ldrb.w ip, [r1, #1] >> >> 8154: ldrb r3, [r4, #1] >> >> 8156: cmp r3, ip &gt...

...8142: bne.n 8168 <foo+0x44> > > > > 8144: ldrb.w ip, [r1, #2] > > 8148: ldrb r3, [r4, #2] > > 814a: cmp r3, ip > > 814c: it ne > > 814e: popne {r4, r6, r7, pc} // a > function return > > > > 8150: ldrb.w ip, [r1, #1] > > 8154: ldrb r3, [r4, #1] > > 8156: cmp r3, ip > > 8158: b...

...'){ + seq_puts(seq, ",subvol="); + seq_puts(seq, vfs->mnt_root->d_name.name); + } + spin_unlock(&vfs->mnt_root->d_lock); return 0; } -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512

Currently the resize command is under filesystem, and takes a path to the mounted filesystem. This seems wrong to me. Shouldn''t it be under device, and take a path to a device to resize? Otherwise, how can a resize operation when you have multiple devices make any sense? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

...bne.n 8168 <foo+0x44> > > > > 8144: ldrb.w ip, [r1, #2] > > 8148: ldrb r3, [r4, #2] > > 814a: cmp r3, ip > > 814c: it ne > > 814e: popne {r4, r6, r7, pc} // a function return > > > > 8150: ldrb.w ip, [r1, #1] > > 8154: ldrb r3, [r4, #1] > > 8156: cmp r3, ip > > 8158:...

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 / I define which snapshot to use at the next boot. After rebooting I decide I really want to stay with

...." sync sleep 5s sync echo "Remove $ROLLBACK" btrfs subvolume delete "$ROLLBACK" ------------------------------------------------------------ -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512

Add a mount option user_subvol_rm_allowed that allows users to delete a (potentially non-empty!) subvol when they would otherwise we allowed to do an rmdir(2). We duplicate the may_delete() checks from the core VFS code to implement identical security checks (minus the directory size check). Signed-off-by: Sage Weil <sage@newdream.net> --- fs/btrfs/ctree.h | 1 + fs/btrfs/ioctl.c |

...name = } } protocol imap { mail_plugins = quota acl imap_sieve imap_acl } ---------------------------------------- Does anyone see what I'm doing wrong here? Kind regards, -- Maxime DERCHE Information System Consulting France | NVMQVAM SOLVS https://www.mdisc.fr/ OpenPGP Key ID: 0x814E02A25697FD13 OpenPGP Key Fingerprint: 8B7B 60C9 1095 A198 C883 5205 814E 02A2 5697 FD13 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <https://dovecot.org/pipe...

...BTRFS_IOC_INO_LOOKUP _IOWR(BTRFS_IOCTL_MAGIC, 18, \ struct btrfs_ioctl_ino_lookup_args) [1] http://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg07513.html -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512

Thanks for the quick reply! But I still have problems with btrfsctl: > stat /dev/btrfs-control File: `/dev/btrfs-control'' Size: 0 Blocks: 0 IO Block: 4096 block special file Device: ch/12d Inode: 659848 Links: 1 Device type: a,3e Access: (0644/brw-r--r--) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2010-01-09 11:31:15.757979602 +0100

Hi, Let me know if this is the wrong place to ask... I''m using Fedora 12 x86_64, mostly with the newer 21.6.32 kernel, and have a single btrfs filesystem within a 120Gb partition. I''d like to extend the space btrfs can use. One option is presumably add a new device to btrfs, but I was hoping to simple resize the existing partition to say 160Gb. With ext4 I might do

...table for any uses other than benchmarking and review. +Please refer to the btrfs wiki http://btrfs.wiki.kernel.org for +further details. +.SH SEE ALSO +.BR mkfs.btrfs (8) -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512

...9;t know the changes which may be required to work for other distributions (like fedora), but I am very interested in knowing those. Comments are welcome. BR Goffredo -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512 -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

On Sun, Feb 21, 2010 at 8:40 AM, Goffredo Baroncelli <kreijack@gmail.com> wrote: >       filesystem resize [+/-]<size>[gkm]|max <filesystem> -filesystem resize [+/-]<size>[gkm]|max <filesystem> +filesystem resize [+/-]<size>[gkm]|max <dev> This command works on devices, not paths. >              Resize a filesystem identified by <path>.  The

- Add incompat flag, otherwise btrfs-progs will report error when operating on btrfs filesystems mounted with lzo option. - Allow to turn on lzo compression for defrag operation: # btrfs filesystem defragment -c[zlib, lzo] <file> Note: "-c zlib" will fail, because that''s how getopt() works for optional arguments. Signed-off-by: Li Zefan

Hi Anthony, I think that for you may be interested to read this thread http://kerneltrap.org/mailarchive/linux-btrfs/2009/11/20/6588643/thread and to read a my blog about this argument http://kreijack.blogspot.com/2010/01/linux-btrfs-example-of-layout.html Regards Goffredo >----Messaggio originale---- >Da: anthony@extof.me >Data: 19/05/2010 8.50 >A: