Hi Jeff Wu
[root@ceph_client 1]# dd if=/dev/zero of=/1/512M bs=1M count=512
dd: opening `/1/512M': Permission denied
[root@ceph_client 1]#
But it can read and write existing documents.
My configuration is :
;
; Sample ceph ceph.conf file.
;
; This file defines cluster membership, the various locations
; that Ceph stores data, and any other runtime options.
; If a 'host' is defined for a daemon, the start/stop script will
; verify that it matches the hostname (or else ignore it). If it is
; not defined, it is assumed that the daemon is intended to start on
; the current host (e.g., in a setup with a startup.conf on each
; node).
; The variables $type, $id and $name are available to use in paths
; $type = The type of daemon, possible values: mon, mds and osd
; $id = The ID of the daemon, for mon.alpha, $id will be alpha
; $name = $type.$id
; For example:
; osd.0
; $type = osd
; $id = 0
; $name = osd.0
; mon.beta
; $type = mon
; $id = beta
; $name = mon.beta
; global
[global]
; enable secure authentication
auth supported = cephx
keyring = /etc/ceph/keyring.bin
debug ms = 0;
; allow ourselves to open a lot of files
max open files = 131072
; set log file
log file = /var/log/ceph/$name.log
; log_to_syslog = true ; uncomment this line to log to syslog
; set up pid files
pid file = /var/run/ceph/$name.pid
; If you want to run a IPv6 cluster, set this to true.
Dual-stack isn't possible
;ms bind ipv6 = true
; monitors
; You need at least one. You need at least three if you want to
; tolerate any node failures. Always create an odd number.
[mon]
mon data = /data/mon$id
; If you are using for example the RADOS Gateway and want to
have your newly created
; pools a higher replication level, you can set a default
;osd pool default size = 3
; You can also specify a CRUSH rule for new pools
; Wiki: http://ceph.newdream.net/wiki/Custom_data_placement_with_CRUSH
;osd pool default crush rule = 0
; Timing is critical for monitors, but if you want to allow
the clocks to drift a
; bit more, you can specify the max drift.
;mon clock drift allowed = 1
; Tell the monitor to backoff from this warning for 30 seconds
;mon clock drift warn backoff = 30
; logging, for debugging monitor crashes, in order of
; their likelihood of being helpful :)
debug ms = 1
debug mon = 20
debug paxos = 20
debug auth = 20
[mon.0]
host = ceph_mon0
mon addr = 192.168.0.211:6789
; mds
; You need at least one. Define two to get a standby.
[mds]
; where the mds keeps it's secret encryption keys
keyring = /etc/ceph/keyring.$name
; mds logging to debug issues.
debug ms = 1
debug mds = 20
[mds.alpha]
host = ceph_mds0
; osd
; You need at least one. Two if you want data to be replicated.
; Define as many as you like.
[osd]
; This is where the btrfs volume will be mounted.
osd data = /data/$name
keyring = /etc/ceph/keyring.$name
debug osd = 1
debug filestore = 1
; Ideally, make this a separate disk or partition. A few
; hundred MB should be enough; more if you have fast or many
; disks. You can use a file under the osd data dir if need be
; (e.g. /data/$name/journal), but it will be slower than a
; separate disk or partition.
; This is an example of a file-based journal.
osd journal = /data/$name/journal
osd journal size = 1000 ; journal size, in megabytes
; If you want to run the journal on a tmpfs, disable DirectIO
;journal dio = false
; You can change the number of recovery operations to speed up recovery
; or slow it down if your machines can't handle it
; osd recovery max active = 3
; osd logging to debug osd issues, in order of likelihood of being
; helpful
debug ms = 1
debug osd = 20
debug filestore = 20
debug journal = 20
[osd.0]
host = ceph_osd0
; if 'btrfs devs' is not specified, you're responsible for
; setting up the 'osd data' dir. if it is not btrfs, things
; will behave up until you try to recover from a crash (which
; usually fine for basic testing).
btrfs devs = /dev/sda7
; If you want to specify some other mount options, you can do so.
; The default values are rw,noatime
btrfs options = rw,noatime
[osd.1]
host = ceph_osd1
btrfs devs = /dev/sda7
btrfs options = rw,noatime
[client]
; userspace client
debug ms = 1
debug client = 10
2011/6/1 Jeff Wu <[email protected]>:
>
> Hi,
>
> Are the other write commands also printf "Permission denied" ?
>
> Could you try to run:
>
> dd if=/dev/zero of=/1/512M bs=1M count=512
>
> If you detect a bug ,you can file it at
>
> http://tracker.newdream.net
>
> Jeff ,Wu
>
>
> On Wed, 2011-06-01 at 15:19 +0800, biyan chen wrote:
>> 2011-06-01 15:20:23.258669 7fee67a8c710 -- 192.168.0.211:6789/0 <==
>> mds0 192.168.0.207:6800/7272 193 ==== mdsbeacon(4297/alpha up:active
>> seq 180 v14) v2 ==== 244+0+0 (3951961624 0 0) 0x8e1a00 con 0x8efb40
>> 2011-06-01 15:20:23.258706 7fee67a8c710 mon.0@0(leader) e1 have connection
>> 2011-06-01 15:20:23.258720 7fee67a8c710 mon.0@0(leader) e1 ms_dispatch
>> existing session MonSession: mds? 192.168.0.207:6800/7272 is openallow
>> rwx for mds? 192.168.0.207:6800/7272
>> 2011-06-01 15:20:23.258728 7fee67a8c710 mon.0@0(leader) e1 caps allow rwx
>> 2011-06-01 15:20:23.258748 7fee67a8c710
>> mon.0@0(leader).paxosservice(mdsmap) dispatch mdsbeacon(4297/alpha
>> up:active seq 180 v14) v2 from mds0 192.168.0.207:6800/7272
>> 2011-06-01 15:20:23.258763 7fee67a8c710 mon.0@0(leader).paxos(mdsmap
>> active lc 14) is_readable now=2011-06-01 15:20:23.258758
>> lease_expire=0.000000 has v14 lc 14
>> 2011-06-01 15:20:23.258777 7fee67a8c710 mon.0@0(leader).mds e14
>> preprocess_query mdsbeacon(4297/alpha up:active seq 180 v14) v2 from
>> mds0 192.168.0.207:6800/7272
>> 2011-06-01 15:20:23.258792 7fee67a8c710 mon.0@0(leader).mds e14
>> preprocess_beacon mdsbeacon(4297/alpha up:active seq 180 v14) v2 from
>> mds0 192.168.0.207:6800/7272 compat={},rocompat={},incompat={1=base
>> v0.20,2=client writeable ranges,3=default file layouts on dirs,4=dir
>> inode in separate object}
>> 2011-06-01 15:20:23.258806 7fee67a8c710 mon.0@0(leader).mds e14
>> _note_beacon mdsbeacon(4297/alpha up:active seq 180 v14) v2 noting
>> time
>> 2011-06-01 15:20:23.258821 7fee67a8c710 -- 192.168.0.211:6789/0 -->
>> 192.168.0.207:6800/7272 -- mdsbeacon(4297/alpha up:active seq 180 v14)
>> v1 -- ?+0 0x9b4c80 con 0x8efb40
>> ^C
>>
>> [root@ceph_mon0 ceph]# tail /var/log/ceph/mon.0.log -f
>> Display the above information ！
>>
>> Thanks!
>>
>> 2011/6/1 biyan chen <[email protected]>:
>> > When I mount ceph after the file system. I want to go to create a
>> > file, but hint permissions problem, cannot write
>> >
>> > In /var/log/ceph log information inside, didn't see more information
>> >
>> > [root@ceph_client /]# df
>> > Filesystem 1K-blocks Used Available Use% Mounted on
>> > /dev/sda1 472658192 20199408 428449108 5% /
>> > tmpfs 1984548 0 1984548 0% /dev/shm
>> > /dev/loop0 3351190 3351190 0 100% /mnt/cdrom
>> > 192.168.0.211:6789:/ 158047232 81920 155843584 1% /1
>> > [root@ceph_client /]# cd /1
>> > [root@ceph_client 1]# echo "1">>1.txt
>> > -bash: 1.txt: Permission denied
>> > [root@ceph_client 1]# cd ..
>> > [root@ceph_client /]# ll
>> > total 112
>> > drwxr-xr-x. 1 root root 0 Jun 1 20:05 1
>> >
>>
>>
>>
>
>
--
name:Riby
mobile:+86 15280267642
company: 百大龙一
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
