search for: ghigo

Hi, on my system the klibc/ash ( 0.197 ) doesn't compile: [ghigo@therra ash]$ pwd /home/ghigo/klibc/klibc-0.197/ash [ghigo@therra ash]$ make [...] gcc -Wp,-MD,.arith_lex.d -mregparm=3 -DREGPARM=3 -march=i386 -Os -g -falign-functions=0 -falign-jumps=0 -falign-loops=0 -nostdinc -iwithprefix include -D__KLIBC__ -DBITSIZE=32 -I../include/arch/i386 -I../include/bi...

Hi, I am compiling a tiny linux kernel 2.6.10 to be used together with linuxbios. The boot phase will go as follows: linuxbios->tiny linux kernel->initramfs The initramfs shall use dhcp to get it's address and then tftp a full featured kernel. This kernel must be started through kexec. I use a tweaked networkdriver in the kernel and cannot use a normal PXE boot. Which files should I

...metadata_ratio value is used. $ cat /proc/mounts rootfs / rootfs rw 0 0 [...] /dev/sdc /tmp/t4 btrfs rw,relatime,metadata_ratio=20 0 0 /dev/sdc /mnt/btrfs btrfs rw,relatime,degraded,metadata_ratio=20,subvol=snap- of-root 0 0 BR G.Baroncelli commit 3d7ea7bbd70a66c4d0f369b2879c503b722e8834 Author: ghigo <ghigo@kreijack.homelinux.net> Date: Thu Jan 14 20:27:41 2010 +0100 Add info about metadata_ratio and subvolume name diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c index 3f9b457..faeaa7f 100644 --- a/fs/btrfs/super.c +++ b/fs/btrfs/super.c @@ -461,6 +461,16 @@ static int btrfs_show_...

Conclusion: DO NOT USE SOFTWARE RAID-1 WITH EXT3 I've started with this conclusion cause i am positive that raid-1 and ext3 are causing data corruption. I've upgraded from 7.1 to 7.2 and from the first date i run into data corruption problems @ least once per day (i was monitoring once per day only) after 7 days we bought a brand new server cause the previous was very old and i thought

...vices, even the ones already scanned. Instead the first option has the disadvantage to need to be used for every new device. From this observation I write a udev rule which scan the new block devices, excluding floppy and cdrom. Below my udev rule $ cat /etc/udev/rules.d/60-btrfs.rules # ghigo 15/04/2010 ACTION!="add|change", GOTO="btrfs_scan_end" SUBSYSTEM!="block", GOTO="btrfs_scan_end" KERNEL!="sd[!0-9]*|hd[!0-9]*", GOTO="btrfs_scan_end" IMPORT{program}="/sbin/blkid -o udev -p $tempnode" # only disk scs...

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

...ber, but a snapshot path from which the command extract the generation number. Examples # btrfs subvolume find-new rootfs/ -s snap-20101207 tmp var/log/exim4/mainlog var/log/kdm.log var/log/daemon.log var/log/kern.log var/log/syslog var/log/messages var/log/wtmp var/log/auth.log var/tmp/kdecache-ghigo/icon-cache.kcache var/tmp/kdecache-ghigo/plasma_theme_default.kcache var/run/utmp var/log/Xorg.0.log var/run/freepops.pid [...] # btrfs subvolume find-new -v snap-20101207 10639 inode 485761 name tmp/paperopoli INODE: mode 0x000041ed gen 12326 nbyte 0 nlink 1 uid 0 gid 0 flags 0x0000 inode 485...

Hello, Sorry if this question is a FAQ, but I don't find it anywere. Does klibc support dynamic linking ? TIA -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = CE3C 7E01 6782 30A3 5B87 87C0 BB86 505C 6B2A CFF9

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

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

...ib/libeatmydata/libeatmydata.so aptitude ) echo "Syncing..." 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 |

...TRFS_IOCTL_MAGIC, 25, \ struct btrfs_ioctl_search_args) #define 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

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

...uses all the disks - - RAID1 uses two different disks Comments are welcome. Known bugs: - - if a filesystem uses a disk but there is any chunk, the disk is not shown (solvable) - - this command need root capability (I use the BTRFS_IOC_TREE_SEARCH to get the chunk info; so that is unavoidable) ghigo@emulato:~$ sudo ./btrfs fi df /mnt/btrfs1/ [sudo] password for ghigo: Path: /mnt/btrfs1 Summary: Disk_size: 9.00GB Disk_allocated: 1.83GB Disk_unallocated: 7.17GB Used: 284.00KB Free_(Estimated): 6.76GB (Max: 8.54GB, min: 4.96GB) Data_to_disk_ratio: 75 % Allocated_...

...gs. Btrfs filesystem is currently under heavy development, +and not suitable 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

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:

...fs_device_already_in_root(struct btrfs_root *root, int fd, int super_offset); char *pretty_sizes(u64 size); +int btrfs_scan_block_devices(int run_ioctl, int checklist); + +#define BTRFSDEVICELIST "/etc/btrfs.devices" + #endif -- gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijack@inwind.it> Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512