From: Brian Foster <bfoster@redhat.com>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Jens Axboe <axboe@fb.com>, Dave Chinner <david@fromorbit.com>,
fstests@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: ramdisk problems in 4.0-rc1? (was Re: [PATCH 1/4] xfs/104: log size too small for 4k sector drives)
Date: Sun, 1 Mar 2015 09:28:41 -0500 [thread overview]
Message-ID: <20150301142840.GA13044@bfoster.bfoster> (raw)
In-Reply-To: <54F2D28C.8070903@plexistor.com>
On Sun, Mar 01, 2015 at 10:49:16AM +0200, Boaz Harrosh wrote:
> On 02/26/2015 07:23 PM, Brian Foster wrote:
> <>
> >
> > Thanks Boaz, but I still see the same behavior with the part_show patch.
> > It seems to be something that broke in systemd on Fedora between
> > versions systemd-218 and systemd-219. The latter is broken on a 3.19
> > kernel as well.
> >
> > I've filed a systemd bug so we'll see what comes of it from that end:
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1196452
> >
> > Brian
> >
>
> Hi Brian
>
> It says in bugzilla (link above) that this issue is "fixed in git" so
> I guess we should be fine ?
>
Yes, I picked up a more recent systemd version and it seems to work fine
now without the patch referenced below.
Brian
> Jens does *not* need to take
> [PATCH] brd: Re-instate ram disk visibility option (part_show)
>
> Please confirm.
>
> Please tell me if there is anything I can help with?
>
> Thanks
> Boaz
>
next prev parent reply other threads:[~2015-03-01 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1424818479-10083-1-git-send-email-david@fromorbit.com>
[not found] ` <1424818479-10083-2-git-send-email-david@fromorbit.com>
[not found] ` <20150225161151.GC28053@bfoster.bfoster>
2015-02-25 22:32 ` ramdisk problems in 4.0-rc1? (was Re: [PATCH 1/4] xfs/104: log size too small for 4k sector drives) Dave Chinner
2015-02-25 23:31 ` Brian Foster
2015-02-25 23:43 ` Dave Chinner
2015-02-26 7:46 ` Boaz Harrosh
2015-02-26 17:23 ` Brian Foster
2015-03-01 8:49 ` Boaz Harrosh
2015-03-01 14:28 ` Brian Foster [this message]
2015-02-27 0:58 ` Dave Chinner
2015-03-01 8:27 ` Boaz Harrosh
2015-03-02 1:09 ` Dave Chinner
2015-03-02 9:40 ` Boaz Harrosh
2015-02-26 8:14 ` [PATCH] brd: Re-instate ram disk visibility option (part_show) Boaz Harrosh
2015-02-26 8:41 ` [PATCH] brd: Only request 4K sectors if DAX is enabled Boaz Harrosh
2015-02-26 8:48 ` Boaz Harrosh
2015-02-27 0:23 ` Dave Chinner
2015-03-01 8:30 ` Boaz Harrosh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150301142840.GA13044@bfoster.bfoster \
--to=bfoster@redhat.com \
--cc=axboe@fb.com \
--cc=boaz@plexistor.com \
--cc=david@fromorbit.com \
--cc=fstests@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).