* Empty directory size greater than zero and can't remove
@ 2012-12-16 2:04 Drunkard Zhang
2012-12-19 1:44 ` Drunkard Zhang
0 siblings, 1 reply; 7+ messages in thread
From: Drunkard Zhang @ 2012-12-16 2:04 UTC (permalink / raw)
To: maillist-linux
I couldn't rm files in ceph, which was backuped files of one osd. It
reports direcory not empty, but there's nothing under that directory,
just the directory itself held some spaces. How could I shoot down the
problem ?
log30 /mnt/bc # ls -aR osd.28/
osd.28/:
. .. osd.28
osd.28/osd.28:
. .. current
osd.28/osd.28/current:
. .. 0.537_head
osd.28/osd.28/current/0.537_head:
. ..
log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
drwxr-xr-x 1 root root 119M Dec 14 19:22 osd.28/osd.28/current/0.537_head
log30 /mnt/bc #
log30 /mnt/bc # rm -rf osd.28/
rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
The cluster seems health:
log3 ~ # ceph -s
health HEALTH_OK
monmap e1: 3 mons at
{log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
osdmap e1864: 45 osds: 45 up, 45 in
pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565 GB
used, 111 TB / 120 TB avail
mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
And this is the pgid info mentioned above:
log3 ~ # ceph pg 0.537 query
{ "state": "active+clean",
"up": [
11,
28,
33],
"acting": [
11,
28,
33],
"info": { "pgid": "0.537",
"last_update": "1864'546",
"last_complete": "1864'546",
"log_tail": "0'0",
"last_backfill": "MAX",
"purged_snaps": "[]",
"history": { "epoch_created": 1,
"last_epoch_started": 1740,
"last_epoch_clean": 1774,
"last_epoch_split": 1524,
"same_up_since": 1738,
"same_interval_since": 1738,
"same_primary_since": 1523,
"last_scrub": "1864'546",
"last_scrub_stamp": "2012-12-16 04:26:16.037585"},
"stats": { "version": "1864'546",
"reported": "1523'3018",
"state": "active+clean",
"last_fresh": "2012-12-16 04:26:16.037742",
"last_change": "2012-12-16 04:26:16.037742",
"last_active": "2012-12-16 04:26:16.037742",
"last_clean": "2012-12-16 04:26:16.037742",
"last_unstale": "2012-12-16 04:26:16.037742",
"mapping_epoch": 1523,
"log_start": "0'0",
"ondisk_log_start": "0'0",
"created": 1,
"last_epoch_clean": 1,
"parent": "0.0",
"parent_split_bits": 0,
"last_scrub": "1864'546",
"last_scrub_stamp": "2012-12-16 04:26:16.037585",
"log_size": 74256,
"ondisk_log_size": 74256,
"stat_sum": { "num_bytes": 1708739453,
"num_objects": 428,
"num_object_clones": 0,
"num_object_copies": 0,
"num_objects_missing_on_primary": 0,
"num_objects_degraded": 0,
"num_objects_unfound": 0,
"num_read": 0,
"num_read_kb": 0,
"num_write": 546,
"num_write_kb": 1889873},
"stat_cat_sum": {},
"up": [
11,
28,
33],
"acting": [
11,
28,
33]},
"empty": 0,
"dne": 0,
"incomplete": 0},
"recovery_state": [
{ "name": "Started\/Primary\/Active",
"enter_time": "2012-12-14 11:03:28.545423",
"might_have_unfound": [],
"recovery_progress": { "backfill_target": -1,
"waiting_on_backfill": 0,
"backfill_pos": "0\/\/0\/\/-1",
"backfill_info": { "begin": "0\/\/0\/\/-1",
"end": "0\/\/0\/\/-1",
"objects": []},
"peer_backfill_info": { "begin": "0\/\/0\/\/-1",
"end": "0\/\/0\/\/-1",
"objects": []},
"backfills_in_flight": [],
"pull_from_peer": [],
"pushing": []},
"scrub": { "scrub_epoch_start": "1738",
"scrub_active": 0,
"scrub_block_writes": 0,
"finalizing_scrub": 0,
"scrub_waiting_on": 0,
"scrub_waiting_on_whom": []}},
{ "name": "Started",
"enter_time": "2012-12-14 11:03:27.525077"}]}
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-16 2:04 Empty directory size greater than zero and can't remove Drunkard Zhang
@ 2012-12-19 1:44 ` Drunkard Zhang
2012-12-19 2:13 ` Mark Kirkwood
0 siblings, 1 reply; 7+ messages in thread
From: Drunkard Zhang @ 2012-12-19 1:44 UTC (permalink / raw)
To: maillist-linux
2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
> I couldn't rm files in ceph, which was backuped files of one osd. It
> reports direcory not empty, but there's nothing under that directory,
> just the directory itself held some spaces. How could I shoot down the
> problem ?
>
> log30 /mnt/bc # ls -aR osd.28/
> osd.28/:
> . .. osd.28
>
> osd.28/osd.28:
> . .. current
>
> osd.28/osd.28/current:
> . .. 0.537_head
>
> osd.28/osd.28/current/0.537_head:
> . ..
> log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
> drwxr-xr-x 1 root root 119M Dec 14 19:22 osd.28/osd.28/current/0.537_head
> log30 /mnt/bc #
> log30 /mnt/bc # rm -rf osd.28/
> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
> log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>
> The cluster seems health:
> log3 ~ # ceph -s
> health HEALTH_OK
> monmap e1: 3 mons at
> {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
> election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
> osdmap e1864: 45 osds: 45 up, 45 in
> pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565 GB
> used, 111 TB / 120 TB avail
> mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
>
After mds restart, I got this error message:
2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
2038=2038+0)
How can I fix this?
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-19 1:44 ` Drunkard Zhang
@ 2012-12-19 2:13 ` Mark Kirkwood
2012-12-19 2:56 ` Drunkard Zhang
0 siblings, 1 reply; 7+ messages in thread
From: Mark Kirkwood @ 2012-12-19 2:13 UTC (permalink / raw)
To: Drunkard Zhang; +Cc: maillist-linux
On 19/12/12 14:44, Drunkard Zhang wrote:
> 2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
>> I couldn't rm files in ceph, which was backuped files of one osd. It
>> reports direcory not empty, but there's nothing under that directory,
>> just the directory itself held some spaces. How could I shoot down the
>> problem ?
>>
>> log30 /mnt/bc # ls -aR osd.28/
>> osd.28/:
>> . .. osd.28
>>
>> osd.28/osd.28:
>> . .. current
>>
>> osd.28/osd.28/current:
>> . .. 0.537_head
>>
>> osd.28/osd.28/current/0.537_head:
>> . ..
>> log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
>> drwxr-xr-x 1 root root 119M Dec 14 19:22 osd.28/osd.28/current/0.537_head
>> log30 /mnt/bc #
>> log30 /mnt/bc # rm -rf osd.28/
>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>> log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>>
>> The cluster seems health:
>> log3 ~ # ceph -s
>> health HEALTH_OK
>> monmap e1: 3 mons at
>> {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
>> election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
>> osdmap e1864: 45 osds: 45 up, 45 in
>> pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565 GB
>> used, 111 TB / 120 TB avail
>> mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
>>
> After mds restart, I got this error message:
> 2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
> single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
> 1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
> 2038=2038+0)
>
> How can I fix this?
>
Is it a btrfs filesystem? If so will have sub volumes hiding in there
you need to remove 1st.
Cheers
Mark
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-19 2:13 ` Mark Kirkwood
@ 2012-12-19 2:56 ` Drunkard Zhang
2012-12-19 3:48 ` Mark Kirkwood
0 siblings, 1 reply; 7+ messages in thread
From: Drunkard Zhang @ 2012-12-19 2:56 UTC (permalink / raw)
To: Mark Kirkwood; +Cc: maillist-linux
2012/12/19 Mark Kirkwood <mark.kirkwood@catalyst.net.nz>:
> On 19/12/12 14:44, Drunkard Zhang wrote:
>>
>> 2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
>>>
>>> I couldn't rm files in ceph, which was backuped files of one osd. It
>>> reports direcory not empty, but there's nothing under that directory,
>>> just the directory itself held some spaces. How could I shoot down the
>>> problem ?
>>>
>>> log30 /mnt/bc # ls -aR osd.28/
>>> osd.28/:
>>> . .. osd.28
>>>
>>> osd.28/osd.28:
>>> . .. current
>>>
>>> osd.28/osd.28/current:
>>> . .. 0.537_head
>>>
>>> osd.28/osd.28/current/0.537_head:
>>> . ..
>>> log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
>>> drwxr-xr-x 1 root root 119M Dec 14 19:22 osd.28/osd.28/current/0.537_head
>>> log30 /mnt/bc #
>>> log30 /mnt/bc # rm -rf osd.28/
>>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>>> log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
>>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>>>
>>> The cluster seems health:
>>> log3 ~ # ceph -s
>>> health HEALTH_OK
>>> monmap e1: 3 mons at
>>>
>>> {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
>>> election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
>>> osdmap e1864: 45 osds: 45 up, 45 in
>>> pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565 GB
>>> used, 111 TB / 120 TB avail
>>> mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
>>>
>> After mds restart, I got this error message:
>> 2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
>> single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
>> 1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
>> 2038=2038+0)
>>
>> How can I fix this?
>>
>
> Is it a btrfs filesystem? If so will have sub volumes hiding in there you
> need to remove 1st.
Thanks for reply, osds all lives on xfs filesystem.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-19 2:56 ` Drunkard Zhang
@ 2012-12-19 3:48 ` Mark Kirkwood
2012-12-19 3:51 ` Sage Weil
0 siblings, 1 reply; 7+ messages in thread
From: Mark Kirkwood @ 2012-12-19 3:48 UTC (permalink / raw)
To: Drunkard Zhang; +Cc: maillist-linux
On 19/12/12 15:56, Drunkard Zhang wrote:
> 2012/12/19 Mark Kirkwood <mark.kirkwood@catalyst.net.nz>:
>> On 19/12/12 14:44, Drunkard Zhang wrote:
>>> 2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
>>>> I couldn't rm files in ceph, which was backuped files of one osd. It
>>>> reports direcory not empty, but there's nothing under that directory,
>>>> just the directory itself held some spaces. How could I shoot down the
>>>> problem ?
>>>>
>>>> log30 /mnt/bc # ls -aR osd.28/
>>>> osd.28/:
>>>> . .. osd.28
>>>>
>>>> osd.28/osd.28:
>>>> . .. current
>>>>
>>>> osd.28/osd.28/current:
>>>> . .. 0.537_head
>>>>
>>>> osd.28/osd.28/current/0.537_head:
>>>> . ..
>>>> log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
>>>> drwxr-xr-x 1 root root 119M Dec 14 19:22 osd.28/osd.28/current/0.537_head
>>>> log30 /mnt/bc #
>>>> log30 /mnt/bc # rm -rf osd.28/
>>>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>>>> log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
>>>> rm: cannot remove ‘osd.28/osd.28/current/0.537_head’: Directory not empty
>>>>
>>>> The cluster seems health:
>>>> log3 ~ # ceph -s
>>>> health HEALTH_OK
>>>> monmap e1: 3 mons at
>>>>
>>>> {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
>>>> election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
>>>> osdmap e1864: 45 osds: 45 up, 45 in
>>>> pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565 GB
>>>> used, 111 TB / 120 TB avail
>>>> mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
>>>>
>>> After mds restart, I got this error message:
>>> 2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
>>> single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
>>> 1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
>>> 2038=2038+0)
>>>
>>> How can I fix this?
>>>
>> Is it a btrfs filesystem? If so will have sub volumes hiding in there you
>> need to remove 1st.
> Thanks for reply, osds all lives on xfs filesystem.
Ah, right - might be worth showing us output of 'ls -la' in the dir
concerned. In particular the link counts might be wrong (indicating fs
corruption, probably fixable with xfs_repair).
Cheers
Mark
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-19 3:48 ` Mark Kirkwood
@ 2012-12-19 3:51 ` Sage Weil
2012-12-19 16:31 ` Drunkard Zhang
0 siblings, 1 reply; 7+ messages in thread
From: Sage Weil @ 2012-12-19 3:51 UTC (permalink / raw)
To: Mark Kirkwood; +Cc: Drunkard Zhang, maillist-linux
On Wed, 19 Dec 2012, Mark Kirkwood wrote:
> On 19/12/12 15:56, Drunkard Zhang wrote:
> > 2012/12/19 Mark Kirkwood <mark.kirkwood@catalyst.net.nz>:
> > > On 19/12/12 14:44, Drunkard Zhang wrote:
> > > > 2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
> > > > > I couldn't rm files in ceph, which was backuped files of one osd. It
> > > > > reports direcory not empty, but there's nothing under that directory,
> > > > > just the directory itself held some spaces. How could I shoot down the
> > > > > problem ?
> > > > >
> > > > > log30 /mnt/bc # ls -aR osd.28/
> > > > > osd.28/:
> > > > > . .. osd.28
> > > > >
> > > > > osd.28/osd.28:
> > > > > . .. current
> > > > >
> > > > > osd.28/osd.28/current:
> > > > > . .. 0.537_head
> > > > >
> > > > > osd.28/osd.28/current/0.537_head:
> > > > > . ..
> > > > > log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
> > > > > drwxr-xr-x 1 root root 119M Dec 14 19:22
> > > > > osd.28/osd.28/current/0.537_head
> > > > > log30 /mnt/bc #
> > > > > log30 /mnt/bc # rm -rf osd.28/
> > > > > rm: cannot remove ?osd.28/osd.28/current/0.537_head?: Directory not
> > > > > empty
> > > > > log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
> > > > > rm: cannot remove ?osd.28/osd.28/current/0.537_head?: Directory not
> > > > > empty
> > > > >
> > > > > The cluster seems health:
> > > > > log3 ~ # ceph -s
> > > > > health HEALTH_OK
> > > > > monmap e1: 3 mons at
> > > > >
> > > > > {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
> > > > > election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
> > > > > osdmap e1864: 45 osds: 45 up, 45 in
> > > > > pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565
> > > > > GB
> > > > > used, 111 TB / 120 TB avail
> > > > > mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
> > > > >
> > > > After mds restart, I got this error message:
> > > > 2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
> > > > single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
> > > > 1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
> > > > 2038=2038+0)
> > > >
> > > > How can I fix this?
> > > >
> > > Is it a btrfs filesystem? If so will have sub volumes hiding in there you
> > > need to remove 1st.
> > Thanks for reply, osds all lives on xfs filesystem.
>
> Ah, right - might be worth showing us output of 'ls -la' in the dir concerned.
> In particular the link counts might be wrong (indicating fs corruption,
> probably fixable with xfs_repair).
This is a problem in the MDS, not the fs underneath the OSDs. There was
at least one bug that was corrupting the 'rstats' recursive info that
could lead to this that has been fixed recently.
The MDS is actually repairing this as it goes, unless you specify the 'mds
verify scatter = true' option, in which case it will assert and kill
itself.
sage
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: Empty directory size greater than zero and can't remove
2012-12-19 3:51 ` Sage Weil
@ 2012-12-19 16:31 ` Drunkard Zhang
0 siblings, 0 replies; 7+ messages in thread
From: Drunkard Zhang @ 2012-12-19 16:31 UTC (permalink / raw)
To: Sage Weil; +Cc: Mark Kirkwood, maillist-linux
2012/12/19 Sage Weil <sage@inktank.com>:
> On Wed, 19 Dec 2012, Mark Kirkwood wrote:
>> On 19/12/12 15:56, Drunkard Zhang wrote:
>> > 2012/12/19 Mark Kirkwood <mark.kirkwood@catalyst.net.nz>:
>> > > On 19/12/12 14:44, Drunkard Zhang wrote:
>> > > > 2012/12/16 Drunkard Zhang <gongfan193@gmail.com>:
>> > > > > I couldn't rm files in ceph, which was backuped files of one osd. It
>> > > > > reports direcory not empty, but there's nothing under that directory,
>> > > > > just the directory itself held some spaces. How could I shoot down the
>> > > > > problem ?
>> > > > >
>> > > > > log30 /mnt/bc # ls -aR osd.28/
>> > > > > osd.28/:
>> > > > > . .. osd.28
>> > > > >
>> > > > > osd.28/osd.28:
>> > > > > . .. current
>> > > > >
>> > > > > osd.28/osd.28/current:
>> > > > > . .. 0.537_head
>> > > > >
>> > > > > osd.28/osd.28/current/0.537_head:
>> > > > > . ..
>> > > > > log30 /mnt/bc # ls -lhd osd.28/osd.28/current/0.537_head
>> > > > > drwxr-xr-x 1 root root 119M Dec 14 19:22
>> > > > > osd.28/osd.28/current/0.537_head
>> > > > > log30 /mnt/bc #
>> > > > > log30 /mnt/bc # rm -rf osd.28/
>> > > > > rm: cannot remove ?osd.28/osd.28/current/0.537_head?: Directory not
>> > > > > empty
>> > > > > log30 /mnt/bc # rm -rf osd.28/osd.28/current/0.537_head
>> > > > > rm: cannot remove ?osd.28/osd.28/current/0.537_head?: Directory not
>> > > > > empty
>> > > > >
>> > > > > The cluster seems health:
>> > > > > log3 ~ # ceph -s
>> > > > > health HEALTH_OK
>> > > > > monmap e1: 3 mons at
>> > > > >
>> > > > > {log21=10.205.118.21:6789/0,log3=10.205.119.2:6789/0,squid86-log12=150.164.100.218:6789/0},
>> > > > > election epoch 640, quorum 0,1,2 log21,log3,squid86-log12
>> > > > > osdmap e1864: 45 osds: 45 up, 45 in
>> > > > > pgmap v163907: 9224 pgs: 9224 active+clean; 3168 GB data, 9565
>> > > > > GB
>> > > > > used, 111 TB / 120 TB avail
>> > > > > mdsmap e134: 1/1/1 up {0=log14=up:active}, 1 up:standby
>> > > > >
>> > > > After mds restart, I got this error message:
>> > > > 2012-12-19 09:16:24.837045 mds.0 [ERR] unmatched fragstat size on
>> > > > single dirfrag 100000006c7, inode has f(v6 m2012-11-24 23:18:34.947266
>> > > > 1773=1773+0), dirfrag has f(v6 m2012-12-17 12:43:52.203358
>> > > > 2038=2038+0)
>> > > >
>> > > > How can I fix this?
>> > > >
>> > > Is it a btrfs filesystem? If so will have sub volumes hiding in there you
>> > > need to remove 1st.
>> > Thanks for reply, osds all lives on xfs filesystem.
>>
>> Ah, right - might be worth showing us output of 'ls -la' in the dir concerned.
>> In particular the link counts might be wrong (indicating fs corruption,
>> probably fixable with xfs_repair).
>
Sorry for late response, but I was involved in another stuck problem,
turns out it's firewall rules lost :(
Here's ls of this directory recursively:
log1 /mnt/bc # ls -laR osd.28/
osd.28/:
total 0
drwxr-xr-x 1 root root 124379978 Dec 13 23:04 .
drwxr-xr-x 1 root root 7251593161780 Dec 19 01:05 ..
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 osd.28
osd.28/osd.28:
total 0
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 .
drwxr-xr-x 1 root root 124379978 Dec 13 23:04 ..
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 current
osd.28/osd.28/current:
total 0
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 .
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 ..
drwxr-xr-x 1 root root 124379978 Dec 16 12:40 0.537_head
osd.28/osd.28/current/0.537_head:
total 0
drwxr-xr-x 1 root root 124379978 Dec 16 12:40 .
drwxr-xr-x 1 root root 124379978 Dec 14 19:24 ..
log1 /mnt/bc #
> This is a problem in the MDS, not the fs underneath the OSDs. There was
> at least one bug that was corrupting the 'rstats' recursive info that
> could lead to this that has been fixed recently.
>
> The MDS is actually repairing this as it goes, unless you specify the 'mds
> verify scatter = true' option, in which case it will assert and kill
> itself.
>
So, I can fix this problem by set this option? 'mds verify scatter = true'
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2012-12-19 16:31 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-12-16 2:04 Empty directory size greater than zero and can't remove Drunkard Zhang
2012-12-19 1:44 ` Drunkard Zhang
2012-12-19 2:13 ` Mark Kirkwood
2012-12-19 2:56 ` Drunkard Zhang
2012-12-19 3:48 ` Mark Kirkwood
2012-12-19 3:51 ` Sage Weil
2012-12-19 16:31 ` Drunkard Zhang
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.