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

Data: create/symlink failed, no inodes free. #132

Open
Marietto2008 opened this issue Nov 25, 2022 · 9 comments
Open

Data: create/symlink failed, no inodes free. #132

Marietto2008 opened this issue Nov 25, 2022 · 9 comments

Comments

@Marietto2008
Copy link

Marietto2008 commented Nov 25, 2022

Hello.

I've downloaded the nomadBSD img file from the main site (it is called "nomadbsd-130R-20210508.amd64.img") and I tried increase its space with the truncate command :

truncate -s +200g nomadbsd-130R-20210508.amd64.img

unfortunately it didn't work. I can see that the new size is 204.7 GB,but the internal space of the vm created with this file is still 4.7 GB. In other terms the truncate command failed to work. Is there a workaround for this problem ?

Screenshot_2022-11-25_18-23-27

Screenshot_2022-11-25_18-26-11

@mrclksr
Copy link
Member

mrclksr commented Nov 25, 2022

Did you run truncate after the setup or before?

@Marietto2008
Copy link
Author

Marietto2008 commented Nov 25, 2022

after.

@mrclksr
Copy link
Member

mrclksr commented Nov 25, 2022

This does not work. Run truncate before running the setup.

@Marietto2008
Copy link
Author

It is happened again. I've ran the truncate command before the setup this time,but the size inside the vm hasn't been increased :

Screenshot_2022-11-25_23-25-42

@Marietto2008
Copy link
Author

Marietto2008 commented Nov 25, 2022

Give me your email address please,I will send you the dmesg-log file,maybe you can gather more informations reading inside of it. I can't give you it here,there are sensible informations about my PC that I can't share. Or you can drop me an email here : [email protected]

@mrclksr
Copy link
Member

mrclksr commented Nov 26, 2022

What I see your screenshot is just the size of the root partition which doesn't change anyway. The setup uses all the remaining space to create the /data partition.

@Marietto2008
Copy link
Author

Marietto2008 commented Nov 26, 2022

I've got the error below several times and I've realized that it can be fixed by itself (I got a lot of "write error" errors with a lot of packages,but I've issued more times "pkg upgrade" and the error is gone,but it doesn't for the package below :

Screenshot_2022-11-26_11-24-52

@Marietto2008
Copy link
Author

Marietto2008 commented Nov 26, 2022

maybe you can see the reason of the error from this picture :

Screenshot_2022-11-26_11-46-08

@Marietto2008
Copy link
Author

I've rebooted and it has been able to install the freezed package,but later this is what happened :

https://www.reddit.com/r/freebsd/comments/z55et1/e2fsprogsroothardlinks1465_4_conflicts_with/

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

2 participants