New answers tagged ext4
(I know this is an old question, I came across this problem myself and got my FS back to life without ddrescue, so I'll share the expericence for anyone else encountering this) Ext filesystems store backups of the superblock -- for an occasion just like this one. First, determine the locations of the backups: mke2fs -n /dev/sdxx This is a test run (i.e. ...
There's another case where Birth time will be empty/zero/dash: Ext4's Inode size has to be at least 256bytes to store crtime. The problem occur if you initially created the filesystem smaller than 512MB ( the default Inode size will be 128 bytes, see /etc/mke2fs.conf and mkfs.ext4 manpage). stat -c '%n: %w' testfile testfile: - and/or stat -c '%n: %W' ...
That looks like file system corruption to me; to fix it, do sudo touch /forcefsck and reboot. This will force a fsck of your file systems.
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 ...
According to ceph documents,they recommend configuring Ceph to use the XFS file system in the near term, and btrfs in the long term once it is stable enough for production and at the end, ext4. document 1 document 2 document 3
I pretty much had the same issue, trying to mount gave: $sudo mount /dev/sda2 ./oldfs/ mount: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so I tried the above mentioned re-writing of the part-table, without success. ...
Top 50 recent answers are included