On Di, 04.06.19 12:24, Chris Murphy (li...@colorremedies.com) wrote:
> This is on Fedora Rawhide
> systemd-242-3.git7a6d834.fc31.x86_64
> kernel 5.2.0-0.rc2.git1.2.fc31.x86_64
Please report to the kernel btrfs maintainers, this is not a userspace
problem.
Thanks,
Lennart
--
Lennart P
e an OK thing to do.
>
> What seems strange to me is that in this case the devices don't have changed
> their status.
> How this problem is managed in the md/dm raid cases ?
md has a daemon mdmon to my knowledge.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from thi
On Mon, 15.06.15 19:23, Goffredo Baroncelli (kreij...@inwind.it) wrote:
> On 2015-06-15 12:46, Lennart Poettering wrote:
> > On Sat, 13.06.15 17:09, Goffredo Baroncelli (kreij...@libero.it) wrote:
> >
> >>> Further, the problem will be more intense in this eg. if you u
tl somehow after the
timeout, and then retriggers the devcies so that systemd takes
note. (or, alternatively: such a scheme could even be implemented all
in kernel, based on some configurable kernel setting...)
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the
ev/sdc5" or so. And if I remove or
add backing devices the string really should be updated.
The btrfs client side tools then could use udev to get a list of the
device node symlinks for each device to help the user identifying
which backing devices belong to a btrfs pool.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
it should happen
automatically at all, then it should be triggered by some daemon or
so, but not by udev/systemd.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ese days, if they are missing and on btrfs.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, 23.04.15 19:00, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> On Thu, Apr 23, 2015 at 4:47 PM, Lennart Poettering
> wrote:
> > On Thu, 23.04.15 14:18, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> >
> >> > Pick one:
> >> >
> >&g
awn's --bind= switch, then use yum inside of that
container to install into the btrfs volume. Then get rid of the .raw
image again, and you still have the btrfs volume that should be
bootable.
A bit complex, but you almost were there already... ;-)
Lennart
--
Lennart Poettering, Red Hat
-
On Thu, 23.04.15 14:57, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> On Thu, Apr 23, 2015 at 2:50 PM, Lennart Poettering
> wrote:
> > On Thu, 23.04.15 13:45, arnaud gaboury (arnaud.gabo...@gmail.com) wrote:
> >
> >> Not sure what I did wrong, but I can't
side the raw
fedora image you downloaded. You now have three linuxes, installed
within each other...
Pick one:
a) download the raw image and use that, but it will be a loopback file
with its own file system inside
or:
b) do the dnf/yum install root thing, and install it into a directory
tree.
D
On Mon, 23.03.15 08:36, Chris Mason (c...@fb.com) wrote:
> On Mon, Mar 23, 2015 at 12:57 AM, Lennart Poettering
> wrote:
> >Heya!
> >
> >So what's the story on recursive btrfs snapshotting and snapshot
> >removal? Since a while systemd has now by default creati
Heya!
So what's the story on recursive btrfs snapshotting and snapshot
removal? Since a while systemd has now by default creating btrfs
subvolumes for /var/lib/machines for example. Now, if that code is run
inside a container, and the container itself already is stored in a
subvolume we end up wit
convention for Btrfs subvolumes.
containers are recursively stackable, hence having toplevel subvolumes
doesn't work, since the containers should be able to have
subcontainers of their own...
Also, it kinda defeats the whole point of btrfs' subvolume concept,
where subvolumes are litt
On Thu, 08.01.15 10:56, Zygo Blaxell (ce3g8...@umail.furryterror.org) wrote:
> On Wed, Jan 07, 2015 at 06:43:15PM +0100, Lennart Poettering wrote:
> > Heya!
> >
> > Currently, systemd-journald's disk access patterns (appending to the
> > end of files, then upda
On Wed, 07.01.15 15:10, Josef Bacik (jba...@fb.com) wrote:
> On 01/07/2015 12:43 PM, Lennart Poettering wrote:
> >Heya!
> >
> >Currently, systemd-journald's disk access patterns (appending to the
> >end of files, then updating a few pointers in the front) result
Heya!
Currently, systemd-journald's disk access patterns (appending to the
end of files, then updating a few pointers in the front) result in
awfully fragmented journal files on btrfs, which has a pretty
negative effect on performance when accessing them.
Now, to improve things a bit, I yesterday
ed and it's not ready to just simply add the otime in
> advance.
Exposig this as xattr sounds great to me too.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
Mo
ennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 05.01.15 18:22, Hugo Mills (h...@carfax.org.uk) wrote:
> On Mon, Jan 05, 2015 at 06:15:12PM +0100, Lennart Poettering wrote:
> > Heya,
> >
> > I recently added some btrfs magic to systemd's machinectl/nspawn
> > tool. More specifically it can now sh
Heya!
I am looking for a nice way to query the overall last modification
timestamp of a subvolume. i.e. the most recent mtime of *any* file or
directory within a subvolume. Ideally, I think, there was a
btrfs_timespec field for this in "struct btrfs_root_item", alas there
isn't afaics. Any chance
think it would be good to have an
unprivileged ioctl to query the otime in btrfs... the TREE_SEARCH
ioctl after all requires privileges...)
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to major
Heya,
I recently added some btrfs magic to systemd's machinectl/nspawn
tool. More specifically it can now show the disk usage of a container
that is stored in a btrfs subvolume. For that I made use of the btrfs
quota logic. To read the current disk usage of a subvolume I took
inspiration from btrf
d idea. Instead, requiring one manual step before booting a
degraded array sounds OK to me.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
never really should happen in real-life.
Could anyone who's expereiencing the slowdowns have a look on the
journalctl output menionted above? Do you have more than a few lines
printed like that?
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "
ed at
the beginning of the file to point to the newly appended data. This is
of course not easy to handle for COW file systems. But then again, it's
probably not too different from access patterns of other database or
database-like engines...
Lennart
--
Lennart Poettering, Red Hat
--
To uns
ou take your ideas about our
"attitude" from. God, with behaviour like that you just make us ignore
you, Duncan.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
for reserving space on disk, not for
writing out anything. This is why journald is invoking it, to reserve
the space, so that later write accesses to it will not require any
reservation anymore, and hence are unlikely to fail.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this l
d yeah, I
think I have a very good reason to use fallocate(). The only reason in
fact the man page explicitly mentions.
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
a very good explanation why fallocate() wouldn't be the
right thing to invoke here, and a suggestion what we should do instead
to cover this usecase...
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs"
o ask...
>
> In your specification, you referred the use case of "container" (via
> nspawn / libvrt-lxc). which have to boot "a disk image". Why you don't
> mind to use a container on a btrfs snapshot ? I think that it will be
> reasonable to have different co
s to the admin the problem of combining
subvolumes properly.
Another option would be to introduce a high level concept of a
"subvolume set" or so, which binds subvolumes together, and of which
there could be a "default subvolume set". Within such a subvolume set
could then use type
mple cases only,
and it sounds way over the top to support installing multiple OSes into
the same btrfs... I mean, people can do that, if they want to, they just
have to write a proper fstab, which I think is not too much too ask...
Lennart
--
Lennart Poettering, Red Hat
--
To unsubscribe fr
27;s a at
least one SSD in the fs, resp. at least one rotating disk in the fs.
if (statvfs.f_flag & ST_SSD)
printf("FS contains at least one SSD disk");
if (statvfs.f_flag & ST_ROTATING)
printf("FS contains at least one rotating disk");
Lennart
--
Lennart
ices
if you have a btrfs mount point. This is what Josef's patch added for
us.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
o test for ssd/rotating
properly, instead of just hardcoding a check for
/sys/class/block/sda/queue/rotational.
I hope this explains what the fuck we are doing.
Lennart
--
Lennart Poettering - Red Hat, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
36 matches
Mail list logo
