Skip to content
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

NBD export fail "nbd0: truncated" to mount with block size other than 512 #157

Open
timlee66 opened this issue Mar 11, 2024 · 1 comment

Comments

@timlee66
Copy link

Hi All,
We meet a problem when changing block size from 512 to 1024.

From the dmesg log, we could found that nbd-client be executed with block size 1024. However, we got below error nbd0: truncated and the image seems to be corrupted then mounted iso image: ubuntu-18.04.5-desktop-amd64.iso installation fail. But, if using default block size 512, we can complete installation.

[2024-03-08 11:28:51.819] nbd-client -u /var/run/nbd.558.sock -n -L -t 30 -b 1024 /dev/nbd0
[2024-03-08 11:28:51.819] nbd0: detected capacity change from 0 to 4284224
[2024-03-08 11:28:51.819] nbd0: p1 p2
[2024-03-08 11:28:51.819] nbd0: p1 size 8568448 extends beyond EOD, truncated

Is this the limitation to set block size other than 512?
We try to find some on internet and seems ndb change block size to 512 in this commit: 128fd55

Here is another issue report in Benji. "NBD export fails to mount with default blocksize" that have same error message "truncated".
Related issue refer it: elemental-lf/benji#12

Could someone can help to clarify whether this is limitation for nbd-client change to use other than 512? Thanks.

Sincerely,
Tim

@timlee66
Copy link
Author

Hi All,

There was similar issue from elemental-lf/benji#12
NBD export fails to mount with default blocksize (Previous blocksize is set 1024 as default)
They close this issue due to blocksize set to 512 can work well according below commit.

Related to the blocksize issue; I found:
128fd55

Could someone help us to clarify whether this issue is known issue or something we misunderstand? Thanks.

Best regards,
Tim

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

1 participant