search for: clri

Author: prabahar Repository: /hg/zfs-crypto/gate Revision: 027bdeb71f1847a9969d352a2d0be3ff968b35a9 Log message: 4913439 clri doesn''t first check for ufs superblock magic number before taking action Files: update: usr/src/cmd/fs.d/ufs/clri/clri.c

...dir and such, with the refcount incrementing to 4, and removing it poses no problem, either, with the refcount decrementing back to 3. However 3 is the wrong number. It should of course be only 2 (. and ..) Normally on UFS I would just take the ''nuke it from orbit'' route and use clri to wipe the directory''s inode. However, clri doesn''t appear to be zfs aware (there''s not even a zfs analog of clri in /usr/lib/fs/ zfs), and I don''t immediately see an option in zdb which would help cure this. Any suggestions would be appreciated. /dale

I used ddrescue to copy /dev/md1 to a disk of sufficient size, and re-ran e2fsck, and still get the error message that there's no root file system (I've tried most every superblock): # fsck -y -b 7962624 /dev/sdf fsck 1.36 (05-Feb-2005) e2fsck 1.36 (05-Feb-2005) Superblock has a bad ext3 journal (inode 8). Clear? yes *** ext3 journal has been deleted - filesystem is now ext2 only ***

.../rescue/setfacl 5M /rescue/sh 5M /rescue/stty 5M /rescue/sync 5M /rescue/test 5M /rescue/[ 5M /rescue/rcp 5M /rescue/csh 5M /rescue/tcsh 5M /rescue/atacontrol 5M /rescue/badsect 5M /rescue/camcontrol 5M /rescue/ccdconfig 5M /rescue/clri 5M /rescue/devfs 5M /rescue/dmesg 5M /rescue/dump 5M /rescue/rdump 5M /rescue/dumpfs 5M /rescue/dumpon 5M /rescue/fsck 5M /rescue/fsck_ffs 5M /rescue/fsck_4.2bsd 5M /rescue/fsck_ufs 5M /rescue/fsck_msdosfs 5M /rescue/fsdb 5M /rescue/f...

Hi, The problem started when i installed a kodicom 4400 card and started to run zoneminder. Prior to that no problems with my machine, which now runs FreeBSD panix.internal.net 7.0-RELEASE-p3 FreeBSD 7.0-RELEASE-p3 #3: Mon Jul 14 16:35:37 EEST 2008 doroot@panix.internal.net:/usr/obj/usr/src/sys/GENERIC i386 This hardware change happened in Sunday Jul 13. The next day (Jul 14) morning

Hi, hoping that someone on this list can help me here is the Problem. After a crash it seems the journal could not be recovered. This is what mount gives: root@wuehlkiste:# mount -t ext3 /dev/hdb2 /mnt mount: wrong fs type, bad option, bad superblock on /dev/hdb2, or too many mounted file systems and this is the corresponding logfile-entry: Nov 27 11:16:13 wuehlkiste kernel: attempt to

Sep 21 08:57:54 belle fsck: /dev/ad4s1d: 1 DUP I=190 Sep 21 08:57:54 belle fsck: /dev/ad4s1d: UNEXPECTED SOFT UPDATE INCONSISTENCY; RUN fsck MANUALLY. Ok, so I ran fsck manually (even with -y), but yet it refuses to clear/fix whatever to the questions posed as fsck runs. What does this all mean? Thanks, -Clint -- This message has been scanned for viruses and dangerous content by MailScanner,