12-06-21, 20:52 -
Hi Chris,
Yes, I do have an idea - the docs are not complete
The filesystem (the thing you see with 'df') has not been enlarged yet to the size of the underlying partition.
This has to be done on a reboot following the partition change with fdisk which did the job of making room on the partition for filesystem expansion.
Omitting the size parameter should enlarge the filesystem to all available space.
Not sure whether you need to make the samples partition writeable first.
I would appreciate if you could test this (=is R/W a prereq) and feedback, so that I can complete the docs in a correct way.
This is the first release with the samples on NTFS and this documentation omission escaped correction.
I'm sorry for that and thank you for this feedback!
Regards, Hans
PS: the speed of your old PI may be a problem depending your use, in that case the "clicks & plops" FAQ becomes important. But first have fun getting to know this thing
Yes, I do have an idea - the docs are not complete
The filesystem (the thing you see with 'df') has not been enlarged yet to the size of the underlying partition.
This has to be done on a reboot following the partition change with fdisk which did the job of making room on the partition for filesystem expansion.
Code:
ntfsresize /dev/mmcblk0p3Not sure whether you need to make the samples partition writeable first.
I would appreciate if you could test this (=is R/W a prereq) and feedback, so that I can complete the docs in a correct way.
This is the first release with the samples on NTFS and this documentation omission escaped correction.
I'm sorry for that and thank you for this feedback!
Regards, Hans
PS: the speed of your old PI may be a problem depending your use, in that case the "clicks & plops" FAQ becomes important. But first have fun getting to know this thing
This post was last modified: 12-06-21, 20:53 by hansehv.