Timeline for Can't resize mounted file to dir after increasing size (fallocate)
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 13, 2022 at 21:29 | comment | added | Stephen Kitt | Feel free to write it as an answer, it’s perfectly OK to answer one’s question oneself! | |
| Jan 13, 2022 at 20:39 | history | edited | alchemy | CC BY-SA 4.0 |
added 592 characters in body
|
| Jan 13, 2022 at 20:33 | comment | added | alchemy |
@StephenKitt, thanks for the comment.. lsblk did help me find the /tmpfile wasnt expanded from 30M to 300M because it is in human readable by default. (I couldve swore I used df -h to verify). Anyway, it does work now. Not sure what the difference is/was. I did follow the other link this time after you pointed out it is mounted to a loop device even without the mount -o loop option, thanks. I'll edit in what I did and you can use that as an answer if you like.
|
|
| Jan 13, 2022 at 20:28 | comment | added | alchemy | @icarus I'm trying /tmp first before resizing /home/user, so I want to avoid mkfs. It did finally work with resize2fs when using it on the /dev/loop1 device. | |
| Jan 13, 2022 at 5:37 | comment | added | Stephen Kitt |
You are using a loop device, it was set up for you automatically. lsblk should show it, and then you can follow the answer to the linked question to solve your problem.
|
|
| Jan 13, 2022 at 3:43 | comment | added | icarus | The size will be determined by the filesystem on it. This suggests that using resize2fs was probably the correct approach. Maybe, since this is for /tmp, jusr run mkfs.ext4 on the file as you probably don't need any of the existing files. The file should not be mounted whilst you are doing this. | |
| Jan 13, 2022 at 3:25 | history | edited | alchemy | CC BY-SA 4.0 |
edited title
|
| Jan 13, 2022 at 3:11 | history | asked | alchemy | CC BY-SA 4.0 |