Date: Mon, 26 Jan 2015 18:19:06 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 197023] sysutils/automount 1.4.3 does not work under FreeBSD 10.1 Message-ID: <bug-197023-13-kueFqe50UA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-197023-13@https.bugs.freebsd.org/bugzilla/> References: <bug-197023-13@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197023 --- Comment #7 from vermaden@interia.pl --- > and more importantly - start the disk check > e2fsck -y and so I lost the data on it. cool. Its not an excuse but that is sometimes cost of automation :/ The file(1) is not perfect for filesystem detection. I may also introduce a 'NOFORCE] option to not force the check? You may check the latest 1.5.2 with reworked filesystem detection. The UFS is tried two times because that works best, its tricky (right guess of the filesystem) because if You create two of three new filesystems on the same device without cleaning it with /dev/zero then file(1) shows more then one filesystem detected, 1.5.2 should not be problematic now, but I for sure did not tested every possible configuration out there: # newfs_msdos /dev/md0p1 newfs_msdos: trim 4 sectors to adjust to a multiple of 9 /dev/md0p1: 163712 sectors in 10232 FAT16 clusters (8192 bytes/cluster) BytesPerSec=512 SecPerClust=16 ResSectors=1 FATs=2 RootDirEnts=512 Media=0xf0 FATsecs=40 SecPerTrack=9 Heads=128 HiddenSecs=0 HugeSectors=163836 # newfs /dev/md0p1 /dev/md0p1: 80.0MB (163840 sectors) block size 32768, fragment size 4096 using 4 cylinder groups of 20.03MB, 641 blks, 2688 inodes. super-block backups (for fsck_ffs -b #) at: 192, 41216, 82240, 123264 # file -k -r -b -L -s /dev/md0p1 DOS/MBR boot sector, code offset 0x3c+2, OEM-ID "BSD4.4 ", sectors/cluster 16, root entries 512, sectors/FAT 40, sectors/track 9, heads 128, sectors 163836 (volumes > 32 MB) , serial number 0x791819df, unlabeled, FAT (16 bit) - Unix Fast File system [v2] (little-endian) last written at Thu Jan 1 00:00:00 1970, number of blocks 0, number of data blocks 0, average file size 0, average number of files in dir 0, pending blocks to free 0, pending inodes to free 0, system-wide uuid 0, DOS executable (COM), boot code # mkfs.ext3 /dev/md0p1 mke2fs 1.42.12 (29-Aug-2014) /dev/md0p1 contains a vfat file system Proceed anyway? (y,n) y Creating filesystem with 81920 1k blocks and 20480 inodes Filesystem UUID: b1b58de6-efc2-4531-8576-e732a272d6dd Superblock backups stored on blocks: 8193, 24577, 40961, 57345, 73729 Allocating group tables: done Writing inode tables: done Creating journal (4096 blocks): done Writing superblocks and filesystem accounting information: done # newfs /dev/md0p1 /dev/md0p1: 80.0MB (163840 sectors) block size 32768, fragment size 4096 using 4 cylinder groups of 20.03MB, 641 blks, 2688 inodes. super-block backups (for fsck_ffs -b #) at: 192, 41216, 82240, 123264 # file -k -r -b -L -s /dev/md0p1 Unix Fast File system [v2] (little-endian) last written at Thu Jan 1 00:00:00 1970, number of blocks 0, number of data blocks 0, pending blocks to free 0, system-wide uuid 0, - Linux rev 1.0 ext3 filesystem data, UUID=b1b58de6-efc2-4531-8576-e732a272d6dd -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-197023-13-kueFqe50UA>