gconcat, growfs followed by fsck and errors
Jeremy C. Reed
reed at reedmedia.net
Sat Mar 18 00:35:52 UTC 2006
I don't know if this is geom related. Feel free to point me elsewhere.
I used gconcat to grow a volume. Then I used growfs. It appeared to be
fine and usable.
But I read that using fsck is a good idea. But fsck complained:
fsck: Could not determine filesystem type
So I used fsck_ufs and it showed many, many errors, such as
UNKNOWN FILE TYPE I=124802
and many others.
I now notice that fsck "fsck: Could not determine filesystem type" even
after a newfs of a /dev/label/MYVOLUME. fsck_ufs completed fine.
After converting new /dev/label/MYVOLUME using:
glacier# gconcat label MYVOLUME /dev/ad0s2 /dev/md1
glacier# growfs /dev/concat/MYVOLUME
We strongly recommend you to make a backup before growing the Filesystem
Did you backup your data (Yes/No) ? Yes
new file systemsize is: 568919 frags
Warning: 138716 sector(s) cannot be allocated.
growfs: 1043.4MB (2136960 sectors) block size 16384, fragment size 2048
using 14 cylinder groups of 74.53MB, 4770 blks, 9600 inodes.
super-block backups (for fsck -b #) at:
610720, 763360, 916000, 1068640, 1221280, 1373920, 1526560, 1679200, 1831840,
1984480
glacier# fsck /dev/concat/MYVOLUME
fsck: Could not determine filesystem type
glacier# fsck_ufs /dev/concat/MYVOLUME
** /dev/concat/MYVOLUME
** Last Mounted on
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
UNREF FILE I=126527 OWNER=1227754098 MODE=62157
SIZE=0 MTIME=Dec 31 16:00 1969
RECONNECT? [yn]
CLEAR? [yn] n
UNREF FILE I=126553 OWNER=538976266 MODE=25453
SIZE=0 MTIME=Dec 31 16:00 1969
RECONNECT? [yn] n
CLEAR? [yn] n
UNREF FILE I=127462 OWNER=1327525490 MODE=62562
SIZE=0 MTIME=Dec 31 16:00 1969
RECONNECT? [yn] ^C
***** FILE SYSTEM MARKED DIRTY *****
What can I use to see what these unreferenced files are?
What is strange is in this example above, I did a newfs and fsck
immediately before using gconcat and growfs. So in other words, these
should be empty filesystems with no inodes.
By the way, is using /dev/md* as a geom provider a bad idea?
Jeremy C. Reed
echo ':6DB6=88>?;@69876tA=AC8BB5tA6487><' | tr '4-F' 'wu rofIn.lkigemca'
More information about the freebsd-geom
mailing list