Hi Sage,
I think we can process the write in the following steps,
(1) Submit transaction A to journal, include a PGLog update and a
write zero operation at offset, length
(2) Write the object at offset, length
(3) Submit a transaction B to journal, include a PGLog update and the
metadata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Robert,
I have a pull request open for exactly this use case.
https://github.com/ceph/ceph/pull/4911
I find it particularly useful for debugging spec file issues when
running on other operating systems than suse.
The pull request gives two
On Thu, 18 Jun 2015, Li Wang wrote:
Hi Sage,
I think we can process the write in the following steps,
(1) Submit transaction A to journal, include a PGLog update and a
write zero operation at offset, length
(2) Write the object at offset, length
(3) Submit a transaction B to journal,
Hi Milan-
On Thu, 18 Jun 2015, Milan Broz wrote:
On 06/17/2015 06:16 AM, Sage Weil wrote:
The wiki logins are broken, but ignore that.. we're moving to
tracker.ceph.com's wiki shortly anyway. Email is best in the meantime!
This proposal seems not have to have it to the new wiki. Is it
Hi Yehuda, Kyle,
Based on previous discussions regarding Response for Bucket Creation
by user which is already owned by him, I have come up with following
scenario and proposed solution:
We are trying to match RGW S3 responses with AWS S3 responses.
AWS S3 gives/shows different
I'm also seeing a failure of this in my teuthology run.
-Original Message-
From: ceph-devel-ow...@vger.kernel.org
[mailto:ceph-devel-ow...@vger.kernel.org] On Behalf Of David Zafman
Sent: Friday, June 19, 2015 7:13 AM
To: Gregory Farnum; ceph-devel@vger.kernel.org
Subject: rsyslogd
1 Submit transaction A into journal, mark a offset, length
non-journaling data write in pglog (peering) or omap/xattrs(scrub)
2 Write data to object
3 Submit transaction B into journal, to update the metadata as well as
pglog as usual
I think the problem is far from severe, as long as one OSD
Hi,
I will be raising a pull request. Please merge the code if you feel
everything fine.
On Thu, Jun 18, 2015 at 11:28 PM, Harshal Gupta
harshal.gupta...@gmail.com wrote:
Hi,
I collaborated with Robin on this and finally came with the
implementation which will provide backward compatibility
Hey Cephers,
So it looks like we have the list of approved attendees for the Ceph
Hackathon in Hilsboro, OR that Intel is being kind enough to host.
http://pad.ceph.com/p/hackathon_2015-08
If you are not on that list and would like to be, please contact me as
soon as possible to see if we can
Hi,
I collaborated with Robin on this and finally came with the
implementation which will provide backward compatibility for the
existing users and is configurable for new users.
Also the strictness levels can be further extended if we wish to
further impose more restrictions over naming
Hey cephers,
The schedule and videoconference details have been added to the CDS Jewel page.
http://tracker.ceph.com/projects/ceph/wiki/CDS_Jewel
If you see any problems with my timezone math or have a scheduling
conflict that wont allow you to attend your blueprint session, please
let me know.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Cool, I'll have to give it a shot.
-
Robert LeBlanc
GPG Fingerprint 79A2 9CA4 6CC4 45DD A904 C70E E654 3BB2 FA62 B9F1
On Thu, Jun 18, 2015 at 7:44 AM, Owen Synge wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
sounds good!
- Original Message -
From: Sage Weil s...@newdream.net
To: Yuri Weinstein ywein...@redhat.com
Cc: se...@ceph.com, ceph-devel@vger.kernel.org, Loic Dachary
ldach...@redhat.com, Xinxin Shu xinxin@intel.com, Alfredo Deza
ad...@redhat.com
Sent: Thursday, June 18, 2015
Greg,
Have you changed anything (log rotation related?) that would uninstall
or cause rsyslog to not be able to start?
I'm sometimes seeing machines fail with this error probably in
teuthology/nuke.py reset_syslog_dir().
CommandFailedError: Command failed on plana94 with status 1: 'sudo
Hey Owen,
I suggest we create a wip-systemd branch where we pile in all of the fixes
around getting systemd working properly. Right now we're super
conservative about merging into master to avoid breaking things but it'll
be easier to test everything all at once and it'll help me get packages
-Original Message-
From: ceph-devel-ow...@vger.kernel.org [mailto:ceph-devel-
ow...@vger.kernel.org] On Behalf Of Dan van der Ster
Hi all,
We've recently experienced a broken router than was corrupting packets in
way that the tcp checksums were still valid. There has been some
Hi all,
We've recently experienced a broken router than was corrupting packets
in way that the tcp checksums were still valid. There has been some
resulting data corruption -- thus far the confirmed corruptions were
outside of Ceph communications -- but it has made us want to double
check the
On Thu, Jun 18, 2015 at 9:53 AM, Dałek, Piotr
piotr.da...@ts.fujitsu.com wrote:
Actually, all it takes is just to disable CRC in configuration on one node
(or even
daemon). It'll cause to put zeros in CRC fields in all messages sent,
triggering
CRC check failures cluster-wide (on remaining,
18 matches
Mail list logo
