Project

General

Profile

Actions
Copy link

Bug #1031

closed

dev node inconsistency between cfuse and kernel client

Added by Alexandre Oliva almost 13 years ago. Updated over 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Sage Weil
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
Severity:
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

A dev node created on a cfuse mount is displayed correctly by ls -l on the same mount point:

crw-rw-rw- 1 root root 1, 3 May 29 2010 /media/shared/backup/phone.bak/dev/null

however, with the same ceph filesystem mounted with the kernel client (tried 2.6.35 and 2.6.38, on x86_64-linux-gnu and mips64el-linux-gnu), I get:

crw-rw-rw- 1 root root 0, 259 2010-05-29 09:52 /media/shared/backup/phone.bak/dev/null

I first noticed this after rsyncing onto a kernel client mount point, and then rsyncing again onto the cfuse mount point. The problem occurs (as expected) in both directions.

I don't know which one was supposed to be correct, but clearly the other needs adjusting to match the on-disk representation.

Actions
Copy link
 #1

Updated by Sage Weil almost 13 years ago

  • Target version set to v0.27.1
Actions
Copy link
 #2

Updated by Sage Weil almost 13 years ago

  • Category set to 11
  • Status changed from New to Resolved
  • Assignee set to Sage Weil

fixed by commit:5ac87ffd36c7a3561266d198726eefc9f6a11036

Actions
Copy link
 #3

Updated by John Spray over 7 years ago

  • Project changed from Ceph to CephFS
  • Category deleted (11)
  • Target version deleted (v0.27.1)

Bulk updating project=ceph category=ceph-fuse issues to move to fs project so that we can remove the ceph-fuse category from the ceph project

Actions
Copy link

Also available in: Atom PDF