From mboxrd@z Thu Jan 1 00:00:00 1970 From: Victor Hooi Subject: Re: Btrfs - Unable to mount, can't read superblock? Date: Mon, 15 Feb 2010 20:57:56 +1100 Message-ID: References: <4B789527.1040309@jp.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Cc: linux-btrfs To: TARUISI Hiroaki Return-path: In-Reply-To: <4B789527.1040309@jp.fujitsu.com> List-ID: Taruisi, Thanks for that. I can't believe it was something as simple as that. It's a laptop, so normally I suspend, But yeah, I've tried rebooting since (actually before your message - but thanks anyway), and it's all good now. Seriously gave me a bit of a shock there. Yes, I know, btrfs isn't stable, but I nearly thought it all went like that, poof *touch wood* =3D). I guess I wasn't used to it not re-mounting after that afte= r an unplug event. Do you know if there's a timeline for device file renaming? I suppose it's not that big a deal now that I'm aware it's not supported. Thanks again for your advice. Cheers, Victor On 15 February 2010 11:28, TARUISI Hiroaki wrote: > Hi, > > This disk was used as /dev/sdd previously, and now it's named > /dev/sdc, isn't it? > If so, you can use this usb disk after reboot, or adjusting > that the disk is recognized as /dev/sdd. > Btrfs does not support device file renaming yet. > > > Regards, > taruisi > > (2010/02/13 21:45), Victor Hooi wrote: >> heya, >> >> This is on kernel 2.6.32.8-1, on Arch Linux 64-bit. I have an extern= al >> harddisk, with a btrfs filessystem on it. Just now, after a reboot, = I >> seem to be unable to mount it. >> >> KDE gives a message about being unable to find the superblock, tryin= g >> to mount it from the command-line gives something similar: >> >>> mount: /dev/sdc1: can't read superblock >> >> I do know the last time I used the disk, it may not have been >> unmounted cleanly. Could that have caused this current issue? Any >> possible remedy? I'm really hoping it is, because that's a 1.5 Tb >> external disk...lol. >> >> Also, dmesg contains: >>> >>> usb 2-2: new high speed USB device using ehci_hcd and address 8 >>> usb 2-2: configuration #1 chosen from 1 choice >>> scsi10 : SCSI emulation for USB Mass Storage devices >>> usb-storage: device found at 8 >>> usb-storage: waiting for device to settle before scanning >>> scsi 10:0:0:0: Direct-Access =A0 =A0 WDC WD15 EADS-00P8B0 =A0 =A0 =A0= =A0 =A0 PQ: 0 ANSI: 2 >>> sd 10:0:0:0: Attached scsi generic sg2 type 0 >>> usb-storage: device scan complete >>> sd 10:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.3= 6 TiB) >>> sd 10:0:0:0: [sdc] Write Protect is off >>> sd 10:0:0:0: [sdc] Mode Sense: 38 00 00 00 >>> sd 10:0:0:0: [sdc] Assuming drive cache: write through >>> sd 10:0:0:0: [sdc] Assuming drive cache: write through >>> =A0sdc: sdc1 >>> sd 10:0:0:0: [sdc] Assuming drive cache: write through >>> sd 10:0:0:0: [sdc] Attached SCSI disk >>> device label tessier-ashpool devid 1 transid 4882 /dev/sdc1 >>> open /dev/sdd1 failed >> >> Cheers, >> Victor >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-btrf= s" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at =A0http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html