linux-ext4 - Inode and Block Allocation Policy

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <0408C81F72528E40A0D3235A1F67FFC804A36B@SN2PRD0202MB144.namprd02.prod.outlook.com>
Date:	Mon, 25 Jun 2012 17:56:17 +0000
From:	"Nelson, John R" <John_Nelson@...dent.uml.edu>
To:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Inode and Block Allocation Policy

i have a quick question about the block allocation in EXT4. I know that EXT4 trys to allocate the files blocks in the files inodes Block Group. But what does EXT4 do when say you have a 100GB Virtualbox image? Does the block allocator just keep allocating blocks in the groups next to the group the files inode is in? Now say that the block group has no blocks but tons of free inodes, does the ext4 allocator use another block group to allocate the inode in or does it use the same block group the directorys inode is in despite no free blocks?
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html