bristol@mailman.lug.org.uk
To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk
You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."
Today's Topics:
1. Inode data allocation (Andrew)
2. Re: Inode data allocation (Chris Boot)
3. Re: Inode data allocation (Shane McEwan)
4. Re: Inode data allocation (Andrew)
5. Re: Inode data allocation (Alex Butcher)
6. Re: Inode data allocation (Andrew)
----------------------------------------------------------------------
Message: 1
Date: Thu, 4 Aug 2016 17:41:29 +0100
From: Andrew <andrewsoltau@gmail.com>
To: Bristol and Bath Group <bristol@mailman.lug.org.uk>
Subject: [bristol] Inode data allocation
Message-ID: <4b7556bb-2a85-1338-eec3-8f32b6f9c739@1dtv.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi
New drive for data. Ext4 is reserving 40gb plus for inode data etc on a
new 3tb drive. Will this shrink down drastically if I store only large
files ie movies on it? The alternative is ntfs as this may wind up being
accessed by windoze but I really do not want to go that route if it all
comes to the same thing once the drive is fairly full.
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20160804/e57eea74/attachment-0001.html>
------------------------------
Message: 2
Date: Thu, 4 Aug 2016 18:34:49 +0100
From: Chris Boot <bootc@bootc.net>
To: andrew@1dtv.com, Andrew <andrewsoltau@gmail.com>, Bristol and Bath
Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Inode data allocation
Message-ID: <c274a209-766b-21af-412f-40be65647737@bootc.net>
Content-Type: text/plain; charset=utf-8
On 2016-08-04 17:41, Andrew via Bristol wrote:
> Hi
>
> New drive for data. Ext4 is reserving 40gb plus for inode data etc on a
> new 3tb drive. Will this shrink down drastically if I store only large
> files ie movies on it? The alternative is ntfs as this may wind up being
> accessed by windoze but I really do not want to go that route if it all
> comes to the same thing once the drive is fairly full.
>
> Andrew
Hi Andrew,
If you know that you won't be needing all those inodes, you can format
the filesystem with options to increase the "inode_ratio", or the ratio
of inodes to storage space. That effectively saves less space for inodes
thus giving you far more space for data storage.
For example:
mkfs.ext4 -T big /dev/sdXY
The various "types" of filesystem are defined in /etc/mke2fs.conf. The
ones you'll be interested in are "big" or "huge" most likely.
"largefile" goes even further, and "largefile4" is just insane.
Things get even more fun when you start approaching 16TB single
filesystems, but I'll leave those stories for another day.
HTH,
Chris
--
Chris Boot
bootc@bootc.net
------------------------------
Message: 3
Date: Thu, 4 Aug 2016 20:58:31 +0100
From: Shane McEwan <shane@mcewan.id.au>
To: bristol@mailman.lug.org.uk
Subject: Re: [bristol] Inode data allocation
Message-ID: <57A39E67.4050601@mcewan.id.au>
Content-Type: text/plain; charset=utf-8; format=flowed
On 04/08/16 18:34, Chris Boot via Bristol wrote:
> If you know that you won't be needing all those inodes, you can format
> the filesystem with options to increase the "inode_ratio", or the ratio
> of inodes to storage space. That effectively saves less space for inodes
> thus giving you far more space for data storage.
Also, by default 5% of the filesystem is reserved for privileged files
(essentially those owned by root). This makes sense for system
partitions where you want the system to keep running even if a user
"fills" the disk. But on a data disk it's just a waste of space. You can
turn off the reservation with:
mkfs.ext4 -m 0 /dev/sdXY
or if you've already started using the filesystem:
tune2fs -m 0 /dev/sdXY
Shane.
------------------------------
Message: 4
Date: Thu, 4 Aug 2016 22:31:51 +0100
From: Andrew <andrewsoltau@gmail.com>
To: Shane McEwan <shane@mcewan.id.au>, Bristol and Bath Linux User
Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Inode data allocation
Message-ID: <9edfd9da-fb17-1e97-5b89-e8a7b34ab665@1dtv.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Thanks guys
mkfs.ext4 -T big /dev/sdXY
took it down to 22.21Gb.
tune2fs -m 0 /dev/sdXY
did not make any difference.
Good enough!
I got the output:
pc # mkfs.ext4 -m 0 /dev/sdc
mke2fs 1.42.12 (29-Aug-2014)
Found a gpt partition table in /dev/sdc
Proceed anyway? (y,n) y
It is not a bootable drive, so should I remove this? If so how?
Andrew
On 04/08/16 20:58, Shane McEwan via Bristol wrote:
> On 04/08/16 18:34, Chris Boot via Bristol wrote:
>> If you know that you won't be needing all those inodes, you can format
>> the filesystem with options to increase the "inode_ratio", or the ratio
>> of inodes to storage space. That effectively saves less space for inodes
>> thus giving you far more space for data storage.
>
> Also, by default 5% of the filesystem is reserved for privileged files
> (essentially those owned by root). This makes sense for system
> partitions where you want the system to keep running even if a user
> "fills" the disk. But on a data disk it's just a waste of space. You
> can turn off the reservation with:
>
> mkfs.ext4 -m 0 /dev/sdXY
>
> or if you've already started using the filesystem:
>
> tune2fs -m 0 /dev/sdXY
>
> Shane.
>
> _______________________________________________
> Bristol mailing list
> Bristol@mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/bristol
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20160804/ea94f8d8/attachment-0001.html>
------------------------------
Message: 5
Date: Fri, 5 Aug 2016 10:14:24 +0100 (BST)
From: Alex Butcher <lug@assursys.co.uk>
To: andrew@1dtv.com, Andrew <andrewsoltau@gmail.com>, Bristol and
Bath Linux User Group <bristol@mailman.lug.org.uk>
Cc: Shane McEwan <shane@mcewan.id.au>
Subject: Re: [bristol] Inode data allocation
Message-ID:
<alpine.LRH.2.11.1608051011260.18868@zlgugi.of5.nffheflf.cev>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Thu, 4 Aug 2016, Andrew via Bristol wrote:
> I got the output:
>
> pc # mkfs.ext4 -m 0 /dev/sdc
> mke2fs 1.42.12 (29-Aug-2014)
> Found a gpt partition table in /dev/sdc
> Proceed anyway? (y,n) y
/dev/sdx (e.g. /dev/sdc) device nodes are whole-disc devices, /dev/sdxn
nodes (e.g. /dev/sdc1) are partitions.
If you create a filesystem on the whole-disc device - which means it won't
have a partition table, whether MBR or GPT - it won't be mountable under
other OSs (*cough* Windows) and will probably require some work to mount
under Linux. Also, if you ever wish to resize the filesystem to allow the
creation of a new filesystem alongside it, you won't be able to.
> Andrew
Best Regards,
Alex
------------------------------
Message: 6
Date: Fri, 5 Aug 2016 11:35:16 +0100
From: Andrew <andrewsoltau@gmail.com>
To: Alex Butcher <lug@assursys.co.uk>, Bristol and Bath Linux User
Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Inode data allocation
Message-ID: <4c1c6d26-f8f4-4d03-9aa3-1527cb004818@1dtv.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 05/08/16 10:14, Alex Butcher via Bristol wrote:
> On Thu, 4 Aug 2016, Andrew via Bristol wrote:
>
>> I got the output:
>>
>> pc # mkfs.ext4 -m 0 /dev/sdc
>> mke2fs 1.42.12 (29-Aug-2014)
>> Found a gpt partition table in /dev/sdc
>> Proceed anyway? (y,n) y
>
> /dev/sdx (e.g. /dev/sdc) device nodes are whole-disc devices, /dev/sdxn
> nodes (e.g. /dev/sdc1) are partitions.
>
> If you create a filesystem on the whole-disc device - which means it
> won't
> have a partition table, whether MBR or GPT - it won't be mountable under
> other OSs (*cough* Windows) and will probably require some work to mount
> under Linux. Also, if you ever wish to resize the filesystem to allow the
> creation of a new filesystem alongside it, you won't be able to.
>
>> Andrew
>
> Best Regards,
> Alex
Hi Alex
Thanks. Doh. So simple but I never twigged the /dev/sdxn.
(Whole disk filesystem automounted fine on linux LMDE2 but of course
windows could not see it. And part of the plan was to connect up to
windows just to copy files over quickly. Saying 19 hours on usb3 so
ethernet would have been a while.
All sorted now with big ext4 on sdc1. Using paragon to see ext4 on
windows which appears to work just fine. But that is only free for 10
days. Anyone know of free software for this?)
Andrew
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.lug.org.uk/mailman/private/bristol/attachments/20160805/e5e3afcc/attachment.html>
------------------------------
Subject: Digest Footer
_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol
------------------------------
End of Bristol Digest, Vol 655, Issue 5
***************************************
Tidak ada komentar:
Posting Komentar