Tag Info

Hot answers tagged

9

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


6

It can be partially accomplished by piping the grep command to lsattr command. lsattr -R | grep +i However, I believe when you mention the entire ext3 file system the search might involve /proc , /dev and some other directories which if reports some error you just want to ignore. You can probably run the command as, lsattr -R 2>/dev/null | grep -- ...


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 ...


4

According to Limits on Table Size the maximum size of a table on Linux 2.4+ using ext3 is 4TB. Since MyISAM stores the row data in one file and the index in another file, I guess this is the maximum theoretical size of the data+index. Since ext3 limits files to 2TB, it doesn't seem possible that the row data could exceed this.


3

There is a specific difference which when we read it twice might make more sense. -p - Automatically repair the file system without any questions. -y - Assume an answer of `yes' to all questions. So fsck -p will try to fix the file system automatically without any user intervention. It is most likely to take decisions such as yes or no by itself. ...


3

To deal with arbitrary file names (including those containing newline characters), the usual trick is to find files inside .//. instead of .. Because // cannot normally occur while traversing the directory tree, you're sure that a // signals the start of a new filename in the find (or here lsattr -R) output. lsattr -R .//. | awk ' function process() { ...


3

Given that the purpose of the script is auditing, it is especially important to deal correctly with arbitrary file names, e.g. with names containing newlines. This makes it impossible to use lsattr on multiple files simultaneously, since the output of lsattr can be ambiguous in that case. You can recurse with find and call lsattr on one file at a time. ...


2

df reports the percentage of used blocks relative to the blocks not reserved for root use (by default I think it's 5% of the drive in ext3). It can be changed by using the -m option of tune2fs e.g. to set it to 2% tune2fs -m 2 /dev/sdXY The reserved blocks allow system daemons to keep going even when the disk is full, while non-root processes will not be ...


2

Thanks to Ramesh, slm and St├ęphane for pointing me in the right direction (I was missing the -R switch for lsattr). Unfortunately, none of the answers so far worked correctly for me. I came up with the following: lsattr -aR .//. | sed -rn '/i.+\.\/\/\./s/\.\/\///p' This protects against newlines being used to make a file appear as being immutable when ...


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}'


1

First, let us use the bytes notation to understand the concepts. Now, the actual size of the external HDD was 850GB which translates to 912680550400 bytes. Block size and fragment size The block size specifies the size that the file-system will use to read and write data. Here the default block size of 4096 bytes is used. The ext3 file system doesn't ...


1

Yes, if your underlying filesystem has a file size limit, then you will get errors in MySQL if you try to add data to the point that your file is full. However, filesystem file size limits are very easily circumvented simply by making your MySQL table PARTITIONed, so that a single table spreads the data over multiple MYD and MYI files. ...


1

Generally, you should follow the guidelines here as mentioned by @Barmar. This lists off limits imposed by various operating systems, but not necessarily for the file systems. And it even has a somewhat misleading listing of "Linux 2.4+ (using ext3 file system) 4TB". There is something else that is very important to consider on an ext3 file system when ...


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

I think you are mixing up two completely different and independent concepts. The large_file feature that you can see in the output of dumpe2fs means that this filesystem can hold files larger than 2 GiB, I think it is set automatically by modern kernels. It has nothing to do with the -T option of mke2fs.



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