Skip to content

Package ceph-fuse is missing #5177

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
DavidZidar opened this issue Sep 20, 2022 · 6 comments
Closed

Package ceph-fuse is missing #5177

DavidZidar opened this issue Sep 20, 2022 · 6 comments

Comments

@DavidZidar
Copy link

Describe the bug

I want to use ceph-fuse which is available in Debian but it is missing.

Steps to reproduce the behaviour

apt install ceph-fuse

Device (s)

Raspberry Pi 3 Mod. B

System

OS

Raspberry Pi reference 2018-10-09
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 7b40fd11bc13d6496bb6bd1bc02f946b7e0ac7cb, stage2

Firmware

Aug 26 2022 14:04:36
Copyright (c) 2012 Broadcom
version 102f1e848393c2112206fadffaaf86db04e98326 (clean) (release) (start)

Kernel

Linux jarvis 5.15.61-v7+ #1579 SMP Fri Aug 26 11:10:59 BST 2022 armv7l GNU/Linux

Logs

No response

Additional context

I asked about ceph-fuse in another related issue but was told the question was just going to be ignored so I'm opening this issue.

@pelwell
Copy link
Contributor

pelwell commented Sep 20, 2022

This isn't the right location to report missing packages - this is for issues regarding the Linux kernel.

However, since this already your second attempt...

The Debian description of the ceph-fuse package says:

Ceph is a distributed network file system designed to provide excellent performance, reliability, and scalability. This is a FUSE-based client that allows one to mount a Ceph file system without root privileges.

Because the FUSE-based client has certain inherent performance limitations, it is recommended that the native Linux kernel client be used if possible. If it is not practical to load a kernel module (insufficient privileges, older kernel, etc.), then the FUSE client will do.

Given that we have added kernel Ceph support, why do you want the slower FUSE equivalent?

@DavidZidar
Copy link
Author

Thanks for the response, my first post was just a question, nothing more. I didn't realize this was the wrong place so thanks for pointing that out.

Regarding ceph-fuse, I've been having issues getting the kernel module to work properly, the FUSE module on the other hand just works and is easier to configure to boot. Since Ceph support is missing on Raspberry Pi I'm currently using an NFSv4 mount instead but it's not been reliable.

@XECDesign
Copy link
Contributor

I want to use ceph-fuse which is available in Debian but it is missing.

It's only available in Debian (and Ubuntu) for amd64. If there's no reason it can't be built for armhf and/or arm64, it should be reported to Debian.

@DavidZidar
Copy link
Author

@XECDesign Oh I see, thanks. I'll have a look there then. But just so I understand, does that mean that if Debian fixes it upstream it would automatically be picked up by Raspbian at some point down the line?

@XECDesign
Copy link
Contributor

Yes, but also if the maintainers of the package verify that there's not reason for it to be disabled, we can pull it into Raspberry Pi OS earlier.

@DavidZidar
Copy link
Author

@XECDesign Cool, I understand, thanks for the help.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants