On Tue, Jun 5, 2012 at 11:28 PM, Andrew Morton
wrote:
> On Tue, 5 Jun 2012 02:46:29 -0700
> Joe Perches wrote:
>
>> KERN_ currently takes up 3 bytes.
>> Shrink the kernel size by using an ASCII SOH and then the level byte.
>> Remove the need for KERN_CONT.
>> Convert directly embedded uses of <.
On Tue, 2012-06-05 at 14:28 -0700, Andrew Morton wrote:
> devkmsg_writev() does weird and wonderful things with
> facilities/levels. That function incorrectly returns "success" when
> copy_from_user() faults, btw.
Oh. Better?
Thanks,
Kay
From: Kay Sievers
Subject: kmsg: /
On Wed, Jun 6, 2012 at 1:35 AM, Joe Perches wrote:
> On Tue, 2012-06-05 at 16:29 -0700, Andrew Morton wrote:
>> What about writes starting with \001n? AFACIT, that will be stripped
>> away and the printk level will be altered. This is new behavior.
>
> Nope.
>
> # echo "\001Hello Andrew" > /dev/
On Wed, Jun 6, 2012 at 1:43 AM, Joe Perches wrote:
> On Wed, 2012-06-06 at 01:39 +0200, Kay Sievers wrote:
>> > # echo "\001Hello Andrew" > /dev/kmsg
>> > /dev/kmsg has
>> > 12,774,2462339252;\001Hello Andrew
>>
>> Try "echo -e"?
On Wed, Jun 6, 2012 at 2:07 AM, Joe Perches wrote:
> On Tue, 2012-06-05 at 16:58 -0700, Andrew Morton wrote:
>> echo "\0014Hello Joe" > /dev/kmsg
>
> # echo -e "\x014Hello Me" > /dev/kmsg
> gives:
> 12,778,4057982669;Hello Me
>
> #echo -e "\x011Hello Me_2" > /dev/kmsg
> gives:
> 12,779,4140452093
On Wed, Jun 6, 2012 at 2:19 AM, Joe Perches wrote:
> On Wed, 2012-06-06 at 02:13 +0200, Kay Sievers wrote:
>> The question is what happens if you inject your new binary two-byte
>> prefix, like:
>> echo -e "\x01\x02Hello" > /dev/kmsg
>
> It's not a
On Wed, Jun 6, 2012 at 2:46 AM, Andrew Morton wrote:
> On Tue, 05 Jun 2012 17:40:05 -0700 Joe Perches wrote:
>
>> On Tue, 2012-06-05 at 17:37 -0700, Andrew Morton wrote:
>> > On Tue, 05 Jun 2012 17:07:27 -0700 Joe Perches wrote:
>> >
>> > > On Tue, 2012-06-05 at 16:58 -0700, Andrew Morton wrote:
I'm currently playing around with native btrfs multi-device support in
systemd. There might be a few "hotplug issues" to solve, here is the
first one:
A mounted (otherwise unused) multi-device volume (USB multi-slot card
reader), hangs at:
$ umount /mnt
with (fedora) kernel
3.6.0-0.rc5.git0.1.
On Mon, Sep 17, 2012 at 7:19 PM, Josef Bacik wrote:
> On Sun, Sep 16, 2012 at 10:07:39PM -0600, Kay Sievers wrote:
>> I'm currently playing around with native btrfs multi-device support in
>> systemd. There might be a few "hotplug issues" to solve, here is the
We are currently playing around with native btrfs multi-device support
in systemd. We already committed the needed pieces to systemd git, to
register all detected btrfs filesystems with the kernel.
For volumes which are listed in fstab for mounting, we delay the
actual mount-attempt of a multi-dev
On Mon, Mar 10, 2014 at 7:34 PM, Goffredo Baroncelli wrote:
> On 03/07/2014 07:26 PM, Lennart Poettering wrote:
>> Since yesterday systemd in git can now discover root, /home, /srv and
>> swap partitions automatically based on GPT type GUIDs, thus making
>> /etc/fstab unnecessary for simple setup
Hey,
I thought it would be a good time good to play around a bit with btrfs
in the usual hotplug setup, so we can - if needed - adapt things
before it is going to be finalized.
At a first look, it looks very promising, and I really like the idea
that the state of the (possibly incomplete) device t
On Thu, Dec 11, 2008 at 02:30, Chris Mason <[EMAIL PROTECTED]> wrote:
> On Tue, 2008-12-09 at 19:02 +0100, Kay Sievers wrote:
>> At a first look, it looks very promising, and I really like the idea
>> that the state of the (possibly incomplete) device tree is kept in t
On Mon, Dec 15, 2008 at 22:03, Andreas Dilger wrote:
> On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
>> The multi-device code uses a very simple brute force scan from userland
>> to populate the list of devices that belong to a given FS. Kay Sievers
>> has some ideas on
On Tue, Dec 16, 2008 at 02:37, Chris Mason wrote:
> On Mon, 2008-12-15 at 23:55 +0100, Kay Sievers wrote:
>> On Mon, Dec 15, 2008 at 22:03, Andreas Dilger wrote:
>> > On Dec 11, 2008 09:43 -0500, Chris Mason wrote:
>> >> The multi-device code uses a very simple
On Tue, Dec 16, 2008 at 20:37, Roland wrote:
> i have come across a weird autocomplete issue i assume it is related to
> btrfs.
>
> let`s have some dirs:
>
> /non-btrfs-mount
> ./linux
> ./testdir
>
> /brtfs-mount
> ./linux
> ./testdir
>
> now, if i do "cd t" in /non-btrfs-mount, "t" autoc
On Tue, Dec 16, 2008 at 21:46, wrote:
>> On Tue, Dec 16, 2008 at 20:37, Roland wrote:
>> > i have come across a weird autocomplete issue i assume it is related to
>> > btrfs.
>> >
>> > let`s have some dirs:
>> >
>> > /non-btrfs-mount
>> > ./linux
>> > ./testdir
>> >
>> > /brtfs-mount
>> >
On Tue, 2008-12-16 at 22:41 +0100, Kay Sievers wrote:
> On Tue, Dec 16, 2008 at 21:46, wrote:
> >> On Tue, Dec 16, 2008 at 20:37, Roland wrote:
> >> > i have come across a weird autocomplete issue i assume it is related to
> >> > btrfs.
> >> >
On Wed, Dec 17, 2008 at 15:17, Chris Mason wrote:
> On Wed, 2008-12-17 at 14:59 +0100, Kay Sievers wrote:
>> On Wed, Dec 17, 2008 at 09:45, Roland wrote:
>> >> On Tue, 2008-12-16 at 22:41 +0100, Kay Sievers wrote:
>> >>>
>> >>> > open(&quo
On Wed, Dec 17, 2008 at 16:08, Christoph Hellwig wrote:
> On Wed, Dec 17, 2008 at 03:50:45PM +0100, Kay Sievers wrote:
>> Sounds all sensible. Btrfs already stores the (possibly incomplete)
>> device tree state in the kernel, which should make things pretty easy
>> for u
On Wed, Dec 17, 2008 at 09:45, Roland wrote:
>> On Tue, 2008-12-16 at 22:41 +0100, Kay Sievers wrote:
>>>
>>> On Tue, Dec 16, 2008 at 21:46, wrote:
>>> >> On Tue, Dec 16, 2008 at 20:37, Roland wrote:
>>> >> > i have come across a weird a
On Wed, Dec 17, 2008 at 14:23, Christoph Hellwig wrote:
> === Notes on support for multiple devices for a single filesystem ===
>
> == Intro ==
>
> Btrfs (and an experimental XFS version) can support multiple underlying block
> devices for a single filesystem instances in a generalized and flexibl
On Wed, Dec 17, 2008 at 21:58, Chris Mason wrote:
> On Wed, 2008-12-17 at 11:53 -0800, Andrew Morton wrote:
>> One thing I've never seen comprehensively addressed is: why do this in
>> the filesystem at all? Why not let MD take care of all this and
>> present a single block device to the fs laye
On Wed, Dec 17, 2008 at 15:46, Kay Sievers wrote:
> On Wed, Dec 17, 2008 at 15:17, Chris Mason wrote:
>> On Wed, 2008-12-17 at 14:59 +0100, Kay Sievers wrote:
>>> On Wed, Dec 17, 2008 at 09:45, Roland wrote:
>>> >> On Tue, 2008-12-16 at 22:41 +0100, Kay Siev
I see the following when disconnecting a USB-stick containing a
mounted 2-partitions btrfs volume, and I try to umount it later.
I reproduced it 3 times, always after a fresh reboot. The box
is unstable after that, modules can not be unloaded, other fs's
can not be unmounted.
Thanks,
Kay
usb 1-
On Fri, Dec 19, 2008 at 01:59, wrote:
>> I see the same issue on x86 32 bit, with the additional __llseek()
>> between the getdents64(), and the last entry returned by readdir
>> ignored.
>
> confirmed - it`s readdir which assumes 32bit.
>
> attached is a sample program which shows the issue on m
On Wed, Jan 7, 2009 at 10:35, David Woodhouse wrote:
> Lifted the first paragraphs of btrfs.txt straight from the wiki...
> +debug-tree: print all of the FS metadata in text form. Example:
Can we please rename that tool and prefix everything with btrfs*,
before anything gets merged into mainlin
On Wed, Jan 14, 2009 at 22:41, Ingo Molnar wrote:
>
> * Ingo Molnar wrote:
>
>> > You just disproved your own case :(
>>
>> how so? 80% is not enough? I also checked Fedora and it has
>> SCHED_DEBUG=y in its kernel rpms.
>
> Ubuntu has CONFIG_SCHED_DEBUG=y as well in their kernels.
$ cat /etc/Su
On Sun, Apr 12, 2009 at 07:35, David Zeuthen wrote:
> But we'd still need some kind of way of having the kernel tell user
> space what devices are currently claimed by the btrfs filesystem
> instance (and we'd need notifications on changes too). Otherwise we
> don't have enough information for th
On Mon, Aug 17, 2009 at 22:47, Mark Lord wrote:
> Chris / list,
>
> stat(2) seems to return invalid major/minor device info
> for btrfs filesystems.
>
> Why? Is this a bug?
This is not invalid and not a bug. It's a superblock without a device,
and expected behavior.
There is no one-to-one relati
On Fri, Jan 8, 2010 at 17:37, Michael Niederle wrote:
> Some btrfs-tools make use of "/dev/btrfs-control".
>
> How should I create this node? Is this a block or a character device (I
> suppose
> it should be a character device), which major and minor numbers should be
> assigned?
It's a char dev
On Fri, Apr 16, 2010 at 20:48, Goffredo Baroncelli wrote:
> 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/ud
On Wed, Sep 29, 2010 at 09:25, Ric Wheeler wrote:
> Second question is why is checking in /sys a big deal, would you prefer an
> interface like we did for alignment in libblkid?
It's about knowing what's behind the 'nodev' major == 0 of a btrfs
mount. There is no way to get that from /sys or an
On Wed, Sep 29, 2010 at 01:25, Christoph Hellwig wrote:
> On Tue, Sep 28, 2010 at 04:53:16PM -0400, Josef Bacik wrote:
>> This was a request from the systemd guys. They need a quick and easy way to
>> get
>> all devices attached to a Btrfs filesystem in order to check if any of the
>> disks
>>
On Thu, Sep 30, 2010 at 01:43, Christoph Hellwig wrote:
> On Wed, Sep 29, 2010 at 10:04:31AM +0200, Kay Sievers wrote:
>> On Wed, Sep 29, 2010 at 09:25, Ric Wheeler wrote:
>>
>> > Second question is why is checking in /sys a big deal, would ??you prefer
>> >
On Thu, Sep 30, 2010 at 21:48, Josef Bacik wrote:
> On Wed, Sep 29, 2010 at 07:43:27PM -0400, Christoph Hellwig wrote:
>> On Wed, Sep 29, 2010 at 10:04:31AM +0200, Kay Sievers wrote:
>> > On Wed, Sep 29, 2010 at 09:25, Ric Wheeler wrote:
>> >
>> > > Secon
36 matches
Mail list logo
