search for: mkfs'd

...eserved blocks gid: 0 (group root) > First inode: 11 > Inode size: 256 > Required extra isize: 28 > Desired extra isize: 28 > Journal inode: 8 > First orphan inode: 8388637 ... Ok, pretty standard, and it appears that you mkfs'd it in april, mounted it, and have never unmounted it. (Nor has it ever crashed, apparently). Also, the last line above shows that there is at least one orphan inode, meaning it's open but unlinked. Blocks aren't freed until it's closed; that may be where all the space is. >...

Hello Eric, thank you for the quick reply and the explanations. > dumpe2fs -h output might show us that. Filesystem volume name: <none> Last mounted on: /opt/ssd Filesystem UUID: 75d6aae6-1746-4260-994b-148dfdb5af95 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype

...week when one of my developer colleagues misconfigured a machine. For NT, you probably need an os which groks ACLS, so it's tar does and just some changes in smbtar/smbclient to make it acl-aware. However! I was always restoring to a filesystem which had been ``formatted'' (mkfs'd) by the native OS. All I had to do was restore while avoiding selected config files (with -X) and without overwriting system files (which were r/o). That means I either ``refreshed'' an existing boot disk that someone had deranged, or I had ``formatted'' and installed the...