similar to: mount error 22 mounting ext3

I am reporting this on the advice of the Fedora Users Mailing List Member. This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. I am reporting this per suggestions made to me on the Fedora Users Mailing List. The following is the mailing list exchange: On 09/18/2014 07:01 PM, Robert Nichols wrote: > On

Hi! I recently tried to mount a filesystem in RAID1 mode using loopback devices. I followed the instructions at [1]. Here''s exactly what I''ve done: $ dd if=/dev/zero of=raid1_0.img bs=1M count=500 $ dd if=/dev/zero of=raid1_1.img bs=1M count=500 $ mkfs.btrfs -m raid1 -d raid1 raid1_0.img raid1_1.img $ losetup /dev/loop0 raid1_0.img $ losetup /dev/loop1 raid1_1.img $ mount -t

Hi, I connected my harddisk which had ext3 filesystem and some files archived in it as slave device and issued "mkfs /dev/hdb2" accidentally. Immediately I issued Ctrl C and stopped the process. But before that it had deleted some 100 Blocks. After that I am unable to boot that hard disk as primary device. The system is asking me "please insert a valid boot device and press

I'm currently working with a testing system that involves running mkfs.ext3 on some pretty large devices on a regular basis. This is getting fairly painful, and I was wondering if there was some way to speed this up. Understood that the end result might be a filesystem that has less of a safety factor (say, fewer superblock backups) but the tradeoff might be worth it in this case. David

Since 2.6.29-rc1 contains btrfs I had to try it. However the loopback mount of my btrfs formatted file fails: user@host:~$ dd if=/dev/zero of=btrfs.img bs=1MB count=512 user@host:~$ mkfs.btrfs btrfs.img fs created label (null) on btrfs.img nodesize 4096 leafsize 4096 sectorsize 4096 size 488.28MB Btrfs v0.16+da35ab2b0b54 user@host:~$ sudo mount -t btrfs -o loop btrfs.img /mnt/btrfs mount:

On Sep 19, 2014, at 7:56 PM, jd1008 <jd1008 at gmail.com> wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to mkfs, and it's subsequent consequences when fsck is run. > > I am reporting this per suggestions made to me on the Fedora Users Mailing List. I would

On Fri, Sep 19, 2014 at 07:56:37PM -0600, jd1008 wrote: > I am reporting this on the advice of the Fedora Users Mailing List Member. > > This the mailing list exchange outlining the problem with specifying -S to > mkfs, > and it's subsequent consequences when fsck is run. If none of the possible superblocks are valid when using mke2fs -b <NNN>, there's a good chance

Hello, this is my scenario: 1)I've created a Pacemaker cluster with the following ocfs package on opensuse 11.3 64bit ocfs2console-1.8.0-2.1.x86_64 ocfs2-tools-o2cb-1.8.0-2.1.x86_64 ocfs2-tools-1.8.0-2.1.x86_64 2)I've configured the cluster as usual : <resources> <clone id="dlm-clone"> <meta_attributes id="dlm-clone-meta_attributes">

Hi, In the ongoing drama surrounding this upgrade, I have encountered another issue that I am unable to currently resolve. mount.ocfs2 /dev/sdb1 /mnt mount.ocfs2: Stale NFS file handle while mounting /dev/sdb1 on /mnt. Check 'dmesg' for more information on this error. dmesg: (3701,1):ocfs2_populate_inode:240 ERROR: file entry generation does not match superblock!

I''ve filed this bug under util-linux, because I think wipefs isn''t deleting all btrfs metadata it could. But ultimately it appears to be a btrfs bug because nothing else sees the stale volume. https://bugzilla.redhat.com/show_bug.cgi?id=889888#c15 btrfs-progs-0.20.rc1.20121017git92d9eec-1.fc18.x86_64 e2fs-progs-1.42.5-1.fc18.x86_64 kernel 3.7.1-2 Brand new 80GB virtual disk,

# uname -a Linux dhcppc1 3.0.1-xxxx-std-ipv6-64 #1 SMP Sun Aug 14 17:06:21 CEST 2011 x86_64 x86_64 x86_64 GNU/Linux mkdir test5 cd test5 dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G losetup /dev/loop2 img5 losetup /dev/loop3 img6 mkfs.btrfs -d raid1 -m raid1 /dev/loop2 /dev/loop3 btrfs device scan btrfs filesystem show Label: none uuid:

Hello, I'm using RedHat 7.2. I needed to mount my root fs to QNX 6.1. QNX supports ext2 only but I tried that anyway. It was mounted wrong (e.g. the /root directory was symbolic link to non-existing file). When I wanted to boot from the RedHat again, these errors occured: ... Mounting root filesystem EXT3: failed to open journal device unknown-block(0,0):-19 mount: error 22 mounting ext3

dd if=/dev/null of=img5 bs=1 seek=2G dd if=/dev/null of=img6 bs=1 seek=2G mkfs.btrfs -d raid1 -m raid1 img5 img6 losetup /dev/loop4 img5 losetup /dev/loop5 img6 btrfs device scan mount -t btrfs /dev/loop4 dir umount dir losetup -d /dev/loop5 mount -t btrfs -o degraded /dev/loop4 dir umount dir losetup -d /dev/loop4 ioctl: LOOP_CLR_FD: Device or resource busy mkfs.ext3 /dev/loop4 mke2fs 1.39

Greetings! Need your help fellow penguins! Strange behavior with fsck.ext3: how to remove a long orphaned inode list? After copying data over from one old RAID to another new RAID with rsync, the dump command would not complete because of filesystem errors on the new RAID. So I ran fsck.ext3 with the -y option and it would just run in an infinite loop restarting itself and then trying to correct

Hello there, I'm a new to linux need help in regards to issues during mounting of a new created logical unit which I am unable to mount the volume due to error as found below: ~]# mount -l -t ext3 /dev/mapper/vgNebula-lvg1 /mnt/iscsi0 mount: wrong fs type, bad option, bad superblock on /dev/mapper/vgNebula-lvg1, missing codepage or helper program, or other error In some cases

Hi, I made an ext3 filesystem with 8kB block size: # mkfs.ext3 -T largefile -v -b 8192 /dev/md0 Warning: blocksize 8192 not usable on most systems. mke2fs 1.38 (30-Jun-2005) Filesystem label= OS type: Linux Block size=8192 (log=3) Fragment size=8192 (log=3) 148480 inodes, 18940704 blocks 947035 blocks (5.00%) reserved for the super user First data block=0 290 block groups 65528 blocks per group,

Hello everybody, I would like your opinion on the following question, why this happens in centos and how to fix this (or a possible work around). I have a drive with no partitions and formatted with xfs filesystem. I give the drive a custom label "mydrive" and I mount it under /dev/mountpnts/mydrive. Then, I add a corresponding entry to fstab. These, are the steps I followed,

Hi, Why does mkfs.ocfs2 take so long compared to gfs2 (pretty fast iirc), xfs (almost instantaneous), or ext3 (slow but still ok)? I'm using: # mkfs.ocfs2 -F -b 4k -C 4k -L san1 -T mail /dev/vg/san1 mkfs.ocfs2 1.3.9 Overwriting existing ocfs2 partition. WARNING: Cluster check disabled. Proceed (y/N): y Filesystem Type of mail Filesystem label=san1 Block size=4096 (bits=12) Cluster size=4096

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode,

Greetings, I''ve had no success with mounting a vfat file system created by a Windows XP guest on a lvm volume. # mount -t vfat /dev/vg1/win1 /mnt/ mount: wrong fs type, bad option, bad superblock on /dev/vg1/win1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so # dmesg FAT: invalid media value (0xb9) VFS: