.com wrote:
> On Sat, Dec 06, 2014 at 08:44:41PM +, Paulo Almeida wrote:
> ...
> > You can also register uids with Debian. Quoting from the Policy
> > Manual[1]:
> >
> > The UID and GID numbers are divided into classes as follows:
> >
> > 0-99:
>
e logs
>
> On Fri, Dec 5, 2014 at 11:32 PM, Paulo Almeida
> wrote:
> > Hi,
> >
> > I recently e-mailed ceph-users about a problem with virtual machine RBD
> > disks remounting read-only because of OSD slow requests[1]. I just
> > wanted to report that a
You can also register uids with Debian. Quoting from the Policy
Manual[1]:
The UID and GID numbers are divided into classes as follows:
0-99:
Globally allocated by the Debian project, the same on every
Debian system. These ids will appear in the passwd and group
f
Hi,
I recently e-mailed ceph-users about a problem with virtual machine RBD
disks remounting read-only because of OSD slow requests[1]. I just
wanted to report that although I'm still seeing OSDs from one particular
machine going down sometimes (probably some hardware problem on that
node), the vi
Hi,
You should be able to use the wheezy-backports repository, which has
ceph 0.80.7.
Cheers,
Paulo
On Sun, 2014-11-30 at 19:31 +0100, Florent MONTHEL wrote:
> Hi,
>
>
> I’m trying to deploy CEPH (with ceph-deploy) on Raspberry Debian 7.6
> and I have below error on ceph-deploy install command
On Fri, 2014-11-28 at 16:37 -0500, Roman Naumenko wrote:
> And if I understand correctly, monitors are the access points to the
> cluster, so they should provide enough aggregated network output for
> all connected clients based on number of OSDs in the cluster?
I'm not sure what you mean by "ac
filesystem superblock, and can be changed using tune2fs(8).
>
>
>
>
> ----- Mail original -
>
> De: "Paulo Almeida"
> À: ceph-users@lists.ceph.com
> Envoyé: Lundi 24 Novembre 2014 17:06:40
> Objet: [ceph-users] Virtual machines using RBD remount read-
that is recommended for KVM guests that would prevent it?
Or does this problem indicate that something else is wrong and should be
fixed? I did configure all machines to use "cache=writeback", but never
investigated whether that makes a difference or even whether it is
actually working.
T