search for: czarc

As of the latest updates to anaconda and grub2 for Fedora 18, it is now possible to install with /boot as a btrfs subvolume. The way that grub2 is handling this is the "reach down" to the files it needs as if the subvolume was a directory. Is this OK? At this point I am not worried about snapshots or any other complexities. If the subvolume name is known. should grub2 be able to

Recently, I had some experiences that raises the question as to how compatible (how safe) it is to mount and then read/write a partition using a system such as FC1 or debian where the partition was created under FC3. 1. I recently attempted to run e2fsck running on a FC1 system against a FC3 ext3 partition ... the program refused to run. When I took the e2fsprogs package from FC3 and

Give some of the messages and bugzilla reports about file system problems which are fixed by using e2fsprogs 1.36, I am curious why an update/errata has not been issued yet. Anyone like to comment on thissituation? Gene

I was looking through some of the archives and notice a patch submitted to implement: btrfs subvolume show <path-to-subvolume> command. I also noticed that is does not appear to be in the git. This looks like a useful capability. I was trying to find out what the UUID was for a newly created subvolume and have not found out how to do that. Gene -- To unsubscribe from this

Some of you may be interested in running your qemu-kvm (or other) disk image files on BTRFS. After some fumbling around, I have found out how to do it so it works and works very well (especially if it is on an SSD). Anyone investigating running on BTRFS immediately finds out that there is a fragmentation problem (just putting image files on btrfs can result in them having between 50,000 and

OK, either I have taken a stupid pill and am missing something basic or routed network do not work. I assume that, if they did work, it would be in more or less that same manner as a nat network as far as ping'ing, ssh'ing, etc. to another real host on the same real LAN as the virtualization host. At least that is what I believe I should expect. I have googled for info and everything

I have had a number of occasions lately where a virtual "NAT" network (such as default) has stopped working. I have attempted to stop and then restart the network from the "network details" but the only thing that seems to work is to restart all of the virtual guests which use that network. I don't believe that I should have to do that. Is there some command which

Given that no 1.36 has appeared from Fedora Core, I thought I would create the rpm myself. I took the 1.35-11.2 src.rpm from FC3 and updated the spec file for 1.36. However, the build fails. Has anyone successfully created a 1.36 rpm for FC3? If so, what did you need to do? Gene