nextcloud / nextcloud/nextcloudpi

[nc-format-usb] partition alignment

Open
#757 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Shell
Stars
2.9k
Forks
318
PR merge metrics
No merged PRs in 30d

Description

Hi everyone,

I am using NextcloudPi on an ODroid HC2 with a SATA attached 4TB WDRed hard drive. The drive was formatted with nc-format-usb as one BTRFS volume, no trouble so far.

But a $ sudo fdisk -l shows the following output:

Disk /dev/sdb: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disklabel type: gpt
Disk identifier: removed by author

Device Start End Sectors Size Type
/dev/sdb1 65535 7814000189 7813934655 3.7T Linux filesystem

Partition 1 does not start on physical sector boundary.

This seems to be no crtical issue, but a performance reduction is observed by other users (not necessarily on NextcloudPi).

Are there any means to avoid the misalignement while using nc-format-usb?

Also I am using an additional HDD plugged in via USB for backup purposes. As a feature request it would be helpful to differentiate the disks in nc-format-usb.

Thanks for feedback, this project is really great.
I wish you all the best for 2019.

Kind regards

funkmastergst

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the nc-format-usb entry point and inspect how it creates the GPT partition shown by fdisk. Reproduce the report with a 4K-sector disk and verify the resulting start sector is aligned; the issue also requests a way to distinguish disks when selecting the formatting target.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux, shell
Domain
cli, operating-systems, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.