From: Gustavo Zacarias gust...@zacarias.com.ar
This commit adds the support for a make variable named
DISABLE_DOCUMENTATION, which allows to disable the build of the
documentation. This is useful in contexts where the tools needed to
build the documentation are not necessarily available.
Hello,
Here are two patches that we have in the Buildroot embedded Linux
build system against btrfs-progs. The first patch allows to disable
the build and installation of the docmentation, the second patch
improves static building and installation.
Thanks,
Thomas
Gustavo Zacarias (1):
Add
This commit improves the static-only building of btrfs-progs, and adds
support for installing the static only tools:
- It now ensures that all programs are built statically, not only a
small subset of them, by defining 'progs_static' from the existing
'progs' variable.
- It changes the
While we're doing a full fsync (when the inode has the flag
BTRFS_INODE_NEEDS_FULL_SYNC set) that is ranged too (covers only a
portion of the file), we might have ordered operations that are started
while we're logging the inode and that fall outside the fsync range.
This means we can get extent
When the fsync callback (btrfs_sync_file) starts, it first waits for
the writeback of any dirty pages to start and finish without holding
the inode's mutex (to reduce contention). After this it acquires the
inode's mutex and repeats that process via btrfs_wait_ordered_range
only if we're doing a
I got a faulty memory module a while ago, and it ran for a while,
corrupting a number of filesystems on that server. Most of the
corruption is long gone, as the filesystems (ceph osds) were
reconstructed, but I tried really hard to avoid having to rebuild one
4TB filesystem from scratch, since it
Introduce support for df to print sizes in KiB, easy to extend to other
bases.
The man page is also updated and fixed in that it made it seem like
multiple paths were accepted.
Signed-off-by: Alexandre Oliva ol...@gnu.org
---
Documentation/btrfs-filesystem.txt |4 +++-
cmds-filesystem.c
Le 28/08/2014 21:40, Konstantinos Skarlatos a écrit :
On 28/8/2014 8:04 μμ, Jean-Denis Girard wrote:
Hi Chris,
Thanks for your detailed answer.
Le 28/08/2014 06:25, Chris Murphy a écrit :
9. btrfs-find-root /dev/sdc
Super think's the tree root is at 29917184, chunk root 20987904
Well
So I commented out the break on line 238 of btrfs-find-root so that it
continues even if it thinks it went past the fs size, rerun the command,
and I finally got a list of blocks to try!
Then as you suggested I did:
for i in `awk '{print $3}' root.txt`
do echo $i
Hello. There seem to be lots of questions in various forums re the
output of btrfs fi df -- especially w.r.t. the usage of the word
total. For example see https://community.oracle.com/thread/2459838
I feel it would make the intent clearer if total were changed to
alloc or allocated (if the short
On 8/30/14, Alexandre Oliva ol...@gnu.org wrote:
Introduce support for df to print sizes in KiB, easy to extend to other
bases.
Hello. I'm glad to see this as I have been a fan of the binary units
for long (since they were introduced)!
However I feel the chosen long option could be improved as
Hey.
For some time now I consider to use btrfs at a larger scale, basically
in two scenarios:
a) As the backend for data pools handled by dcache (dcache.org), where
we run a Tier-2 in the higher PiB range for the LHC Computing Grid...
For now that would be rather boring use of btrfs (i.e. not
12 matches
Mail list logo
