Re: can't read the superbloack

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 19 Jan 2011, Gregory Farnum wrote:
> On Tue, Jan 18, 2011 at 6:38 PM, Qian Wei <hzqianwei@xxxxxxxxx> wrote:
> > Now the my client machine still can't mount the system, the error
> > message is "can't read the superblock ".Moreover, I can use
> > "init-ceph" command to start the system,and the  "cosd cmon cmds" is
> > on process table(so I think the system is running), but I can't  use
> > ?ceph? command to administrate the system, ?2011-01-13 13:27:05.800552
> > b5f41b70 -- :/4555 >> 192.168.178.160:0/0 pipe(0x8429c48 sd=3 pgs=0
> > cs=0 l=0).fault first fault ? is the error message.Do you know what's
> > wrong may cause these problems?
> Well, that "fault first fault" message is very generic so doesn't tell
> us much. However, between that and the superblock error, there's
> clearly some issue about communicating with your monitor. There are a
> few ways to debug this, but let's check out your configuration file...
> > [mon0]
> >        host = cephosd
> >        mon addr = 192.168.178.160
> I'm pretty sure that's your problem. You need to specify a port as
> well. If that doesn't resolve your issues, we can take a deeper look.

Note that the default port is 6789.. you should use that:

	mon addr = 192.168.178.160:6789

sage

[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux