On Tue, Jan 14, 2020 at 11:24 AM Oskar Malnowicz
<oskar.malnowicz@xxxxxxxxxxxxxx> wrote:
>
> $ ceph daemon mds.who flush journal
> {
> "message": "",
> "return_code": 0
> }
>
>
> $ cephfs-table-tool 0 reset session
> {
> "0": {
> "data": {},
> "result": 0
> }
> }
>
> $ cephfs-table-tool 0 reset snap
> {
> "result": 0
> }
>
> $ cephfs-table-tool 0 reset inode
> {
> "0": {
> "data": {},
> "result": 0
> }
> }
>
> $ cephfs-journal-tool --rank=cephfs_test1:0 journal reset
> old journal was 98282151365~92872
> new journal start will be 98285125632 (2881395 bytes past old end)
> writing journal head
> writing EResetJournal entry
> done
>
> $ cephfs-data-scan init
> Inode 0x0x1 already exists, skipping create. Use --force-init to
> overwrite the existing object.
> Inode 0x0x100 already exists, skipping create. Use --force-init to
> overwrite the existing object.
>
> Should i run with --force-init flag ?
No, that shouldn't be necessary.
--
Patrick Donnelly, Ph.D.
He / Him / His
Senior Software Engineer
Red Hat Sunnyvale, CA
GPG: 19F28A586F808C2402351B93C3301A3E258DD79D
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
