mirror of
https://github.com/ceph/ceph
synced 2025-02-23 11:07:35 +00:00
doc: Fix Spelling Error in Developer Guide
Signed-off-by: Li Bingyang <li.bingyang1@zte.com.cn>
This commit is contained in:
parent
7f83a24553
commit
da96cc919c
@ -64,8 +64,8 @@ Testing Blkin
|
||||
|
||||
It's easy to test Ceph's Blkin tracing. Let's assume you don't have
|
||||
Ceph already running, and you compiled Ceph with Blkin support but
|
||||
you did't install it. Then launch Ceph with the ``vstart.sh`` script
|
||||
in Ceph's src directgory so you can see the possible tracepoints.::
|
||||
you didn't install it. Then launch Ceph with the ``vstart.sh`` script
|
||||
in Ceph's src directory so you can see the possible tracepoints.::
|
||||
|
||||
cd src
|
||||
OSD=3 MON=3 RGW=1 ./vstart.sh -n
|
||||
|
@ -118,7 +118,7 @@ out again.
|
||||
|
||||
Hard links
|
||||
----------
|
||||
Inode with multiple hard links is moved to a dummy gloabl SnapRealm. The
|
||||
Inode with multiple hard links is moved to a dummy global SnapRealm. The
|
||||
dummy SnapRealm covers all snapshots in the filesystem. The inode's data
|
||||
will be preserved for any new snapshot. These preserved data will cover
|
||||
snapshots on any linkage of the inode.
|
||||
|
@ -31,7 +31,7 @@ results.
|
||||
The workflows are not enforced when they impose an overhead that does
|
||||
not make sense. For instance, if the release notes for a point release
|
||||
were not written prior to checking all integration tests, they can be
|
||||
commited to the stable branch and the result sent for publication
|
||||
committed to the stable branch and the result sent for publication
|
||||
without going through another run of integration tests.
|
||||
|
||||
Release Cycle
|
||||
|
Loading…
Reference in New Issue
Block a user