Tag Info

Hot answers tagged

8

You can't convert, but can reformat the partition. Boot into Ubuntu or from a live CD and format the partition from there. Be careful not to format the wrong partition. mkfs.ext3 /dev/hdx1


5

The easiest way to do this is to create your backing file as a sparse file; that is, make it 1GB with truncate -s 1G disk.img instead of dd if=/dev/zero bs=1048576 count=1024 of=disk.img (or whatever). Nicely, truncate is also far faster. If you do an ls -l on the file, it'll show as 1GB—but that's only its apparent size. du disk.img will give the actual ...


4

What does commit really do? I think one of the best explanations was given here by allquixotic. Are there really advantages of increasing it (like responsiveness and power savings)? May it actually cause data loss? As per the ext4 official documentation: Ext4 can be told to sync all its data and metadata every 'nrsec' seconds. The default ...


4

The imap command in debugfs can tell you where an inode is. Example: $ debugfs -R 'imap <128901>' /dev/whatever debugfs 1.42.5 (29-Jul-2012) Inode 128901 is part of block group 16 located at block 524344, offset 0x0400 To get a raw dump of inode 128901, you'd seek to byte 524344*block_size + 0x0400 and read inode_size bytes. You can get the ...


3

What Windows (or more precisely NTFS) calls MFT is what typical Unix filesystems call the inode table, and what Windows calls FRN is the inode number. It contains the metadata for a file (permissions, timestamps, etc.), but not the file name (that's part of the directory entries). It also contains the address of the first few blocks of the file, or the ...


2

Firstly, writing a sparse image to a disk will not result in anything but the whole of the size of that image file - holes and all - covering the disk. This is because handling of sparse files is a quality of the filesystem - and a raw device (such as the one to which you write the image) has no such thing yet. A sparse file can be stored safely and securely ...


1

See these 2 pages for a bit more information; they are a bit dated, but should answer some of your questions as far as I can tell: https://www.debian-administration.org/article/643/Migrating_a_live_system_from_ext3_to_ext4_filesystem https://ext4.wiki.kernel.org/index.php/Ext4_Howto#Converting_an_ext3_filesystem_to_ext4


1

The smallest possible allocation size for a file in ext3/ext4 is 0 (none at all) because of inline data: files with sizes smaller than 60 bytes can be stores completely inside the inode itself. Of course, every file, whether it's a regular file, symlink, directory (which can contain data), or character device or block device or named pipe (none of which ...


1

tune2fs -l <filesystem> was what I was looking for. I wrote a command to quickly check the filesystem state for all mounted filesystems: df | awk '/^\/dev/ {print $1}' | xargs -I {} sh -c 'echo {}; tune2fs -l {}' | awk '/^\/dev/ {print $1} /^Filesystem state/ {print $3, " ",$4}'



Only top voted, non community-wiki answers of a minimum length are eligible