Hi, > >>> Hi All, > >>> > >>> Fedora 26 > >>> BIOS boot = legacy (EUFI give me hives) > >>> > >>> I have a SATA backup drive formatted gpt, one partition, xfs. I went into gparted, erased the partition, recreated the partition as ext4 and formatted it as ext4. > >>> > >>> Then I mounted it as ext4, copied some files to it, unmounted it. When I went to remount it, mount told me there was something wrong with ext4. > >> > >> What "something" was that? > > > > mount: /lin-bak: wrong fs type, bad option, bad superblock on /dev/sdd1, missing codepage or helper program, or other error. > > In some cases useful info is found in syslog - try > dmesg | tail or so > ^^^^^^^^^^^^ > > <snip> > > >>> What is the official way to remove an xfs partition? > >> > >> It's not usually needed, but if you don't want the kernel and/or utilities to recognize an xfs block device as xfs anymore, simply zero the first 512 bytes of that block device. > > > > I can do that! > > > > I was concerned about the gpt stuff at the end of the drive. > > Ignored if I clobber the first 512 bytes? > > The filesystem signature on a partition is a separate issue from > the partition table signatures on the disk... > The overall report sounds interesting, the only thing I could think from the top of my head is that ext4 and xfs places superblocks on different locations of the disk (xfs at the very beginning, and ext4 skipping the first 1024bytes). I wonder if for some reason when initializing ext4, the xfs superblock was not wiped out. Maybe some ext4 option to not touch old data and so prevent it to trash out the xfs superblock? Or, as Eric said, a dmesg might be useful, maybe you just have some caching that complete messed up your filesystem initialization? > -Eric -- Carlos -- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
