Re: broken btrfs filesystem

2017-12-12 Thread Austin S. Hemmelgarn

On 2017-12-12 11:24, Hugo Mills wrote:

On Tue, Dec 12, 2017 at 04:18:09PM +, Neal Becker wrote:

Is it possible to check while it is mounted?


Certainly not while mounted read-write. While mounted read-only --
I'm not certain. Possibly.
In theory, it is possible, but I think that the safety measures in 
`btrfs check` don't distinguish between the two cases, so in practice it 
may not be possible.


Hugo.


On Tue, Dec 12, 2017 at 9:52 AM Hugo Mills  wrote:


On Tue, Dec 12, 2017 at 09:02:56AM -0500, Neal Becker wrote:

sudo ls -la ~/
[sudo] password for nbecker:
ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

ls: cannot access '/home/nbecker/.bash_history': No such file or

directory

total 11652
drwxr-xr-x. 1 nbecker nbecker 5826 Dec 12 08:48  .
drwxr-xr-x. 1 rootroot  48 Aug  2 19:32  ..
[...]
-rwxrwxr-x. 1 nbecker nbecker  207 Dec  3  2015  BACKUP.sh
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-rw-r--r--. 1 nbecker nbecker   18 Oct  8  2014  .bash_logout
[...]


Could you show the result of btrfs check --readonly on this FS? The
rest, below, doesn't show up anything unusual to me.

Hugo.


uname -a
Linux nbecker2 4.14.3-300.fc27.x86_64 #1 SMP Mon Dec 4 17:18:27 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

  btrfs --version
btrfs-progs v4.11.1

sudo btrfs fi show
Label: 'fedora'  uuid: 93c586fa-6d86-4148-a528-e61e644db0c8
Total devices 1 FS bytes used 80.96GiB
devid1 size 230.00GiB used 230.00GiB path /dev/sda3

sudo btrfs fi df /home
Data, single: total=226.99GiB, used=78.89GiB
System, single: total=4.00MiB, used=48.00KiB
Metadata, single: total=3.01GiB, used=2.07GiB
GlobalReserve, single: total=222.36MiB, used=0.00B

dmesg.log is here:
https://nbecker.fedorapeople.org/dmesg.txt

mount | grep btrfs
/dev/sda3 on / type btrfs
(rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/root)
/dev/sda3 on /home type btrfs
(rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)







--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: broken btrfs filesystem

2017-12-12 Thread Hugo Mills
On Tue, Dec 12, 2017 at 04:18:09PM +, Neal Becker wrote:
> Is it possible to check while it is mounted?

   Certainly not while mounted read-write. While mounted read-only --
I'm not certain. Possibly.

   Hugo.

> On Tue, Dec 12, 2017 at 9:52 AM Hugo Mills  wrote:
> 
> > On Tue, Dec 12, 2017 at 09:02:56AM -0500, Neal Becker wrote:
> > > sudo ls -la ~/
> > > [sudo] password for nbecker:
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > ls: cannot access '/home/nbecker/.bash_history': No such file or
> > directory
> > > total 11652
> > > drwxr-xr-x. 1 nbecker nbecker 5826 Dec 12 08:48  .
> > > drwxr-xr-x. 1 rootroot  48 Aug  2 19:32  ..
> > > [...]
> > > -rwxrwxr-x. 1 nbecker nbecker  207 Dec  3  2015  BACKUP.sh
> > > -?? ? ?   ?  ??  .bash_history
> > > -?? ? ?   ?  ??  .bash_history
> > > -?? ? ?   ?  ??  .bash_history
> > > -?? ? ?   ?  ??  .bash_history
> > > -?? ? ?   ?  ??  .bash_history
> > > -?? ? ?   ?  ??  .bash_history
> > > -rw-r--r--. 1 nbecker nbecker   18 Oct  8  2014  .bash_logout
> > > [...]
> >
> >Could you show the result of btrfs check --readonly on this FS? The
> > rest, below, doesn't show up anything unusual to me.
> >
> >Hugo.
> >
> > > uname -a
> > > Linux nbecker2 4.14.3-300.fc27.x86_64 #1 SMP Mon Dec 4 17:18:27 UTC
> > > 2017 x86_64 x86_64 x86_64 GNU/Linux
> > >
> > >  btrfs --version
> > > btrfs-progs v4.11.1
> > >
> > > sudo btrfs fi show
> > > Label: 'fedora'  uuid: 93c586fa-6d86-4148-a528-e61e644db0c8
> > > Total devices 1 FS bytes used 80.96GiB
> > > devid1 size 230.00GiB used 230.00GiB path /dev/sda3
> > >
> > > sudo btrfs fi df /home
> > > Data, single: total=226.99GiB, used=78.89GiB
> > > System, single: total=4.00MiB, used=48.00KiB
> > > Metadata, single: total=3.01GiB, used=2.07GiB
> > > GlobalReserve, single: total=222.36MiB, used=0.00B
> > >
> > > dmesg.log is here:
> > > https://nbecker.fedorapeople.org/dmesg.txt
> > >
> > > mount | grep btrfs
> > > /dev/sda3 on / type btrfs
> > > (rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/root)
> > > /dev/sda3 on /home type btrfs
> > > (rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)
> > >
> >

-- 
Hugo Mills | Let me past! There's been a major scientific
hugo@... carfax.org.uk | break-in!
http://carfax.org.uk/  | Through! Break-through!
PGP: E2AB1DE4  |  Ford Prefect


signature.asc
Description: Digital signature


Re: broken btrfs filesystem

2017-12-12 Thread Hugo Mills
On Tue, Dec 12, 2017 at 09:02:56AM -0500, Neal Becker wrote:
> sudo ls -la ~/
> [sudo] password for nbecker:
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> ls: cannot access '/home/nbecker/.bash_history': No such file or directory
> total 11652
> drwxr-xr-x. 1 nbecker nbecker 5826 Dec 12 08:48  .
> drwxr-xr-x. 1 rootroot  48 Aug  2 19:32  ..
> [...]
> -rwxrwxr-x. 1 nbecker nbecker  207 Dec  3  2015  BACKUP.sh
> -?? ? ?   ?  ??  .bash_history
> -?? ? ?   ?  ??  .bash_history
> -?? ? ?   ?  ??  .bash_history
> -?? ? ?   ?  ??  .bash_history
> -?? ? ?   ?  ??  .bash_history
> -?? ? ?   ?  ??  .bash_history
> -rw-r--r--. 1 nbecker nbecker   18 Oct  8  2014  .bash_logout
> [...]

   Could you show the result of btrfs check --readonly on this FS? The
rest, below, doesn't show up anything unusual to me.

   Hugo.

> uname -a
> Linux nbecker2 4.14.3-300.fc27.x86_64 #1 SMP Mon Dec 4 17:18:27 UTC
> 2017 x86_64 x86_64 x86_64 GNU/Linux
> 
>  btrfs --version
> btrfs-progs v4.11.1
> 
> sudo btrfs fi show
> Label: 'fedora'  uuid: 93c586fa-6d86-4148-a528-e61e644db0c8
> Total devices 1 FS bytes used 80.96GiB
> devid1 size 230.00GiB used 230.00GiB path /dev/sda3
> 
> sudo btrfs fi df /home
> Data, single: total=226.99GiB, used=78.89GiB
> System, single: total=4.00MiB, used=48.00KiB
> Metadata, single: total=3.01GiB, used=2.07GiB
> GlobalReserve, single: total=222.36MiB, used=0.00B
> 
> dmesg.log is here:
> https://nbecker.fedorapeople.org/dmesg.txt
> 
> mount | grep btrfs
> /dev/sda3 on / type btrfs
> (rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/root)
> /dev/sda3 on /home type btrfs
> (rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)
> 

-- 
Hugo Mills | Hey, Virtual Memory! Now I can have a *really big*
hugo@... carfax.org.uk | ramdisk!
http://carfax.org.uk/  |
PGP: E2AB1DE4  |


signature.asc
Description: Digital signature


broken btrfs filesystem

2017-12-12 Thread Neal Becker
sudo ls -la ~/
[sudo] password for nbecker:
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
ls: cannot access '/home/nbecker/.bash_history': No such file or directory
total 11652
drwxr-xr-x. 1 nbecker nbecker 5826 Dec 12 08:48  .
drwxr-xr-x. 1 rootroot  48 Aug  2 19:32  ..
[...]
-rwxrwxr-x. 1 nbecker nbecker  207 Dec  3  2015  BACKUP.sh
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-?? ? ?   ?  ??  .bash_history
-rw-r--r--. 1 nbecker nbecker   18 Oct  8  2014  .bash_logout
[...]

uname -a
Linux nbecker2 4.14.3-300.fc27.x86_64 #1 SMP Mon Dec 4 17:18:27 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux

 btrfs --version
btrfs-progs v4.11.1

sudo btrfs fi show
Label: 'fedora'  uuid: 93c586fa-6d86-4148-a528-e61e644db0c8
Total devices 1 FS bytes used 80.96GiB
devid1 size 230.00GiB used 230.00GiB path /dev/sda3

sudo btrfs fi df /home
Data, single: total=226.99GiB, used=78.89GiB
System, single: total=4.00MiB, used=48.00KiB
Metadata, single: total=3.01GiB, used=2.07GiB
GlobalReserve, single: total=222.36MiB, used=0.00B

dmesg.log is here:
https://nbecker.fedorapeople.org/dmesg.txt

mount | grep btrfs
/dev/sda3 on / type btrfs
(rw,relatime,seclabel,ssd,space_cache,subvolid=257,subvol=/root)
/dev/sda3 on /home type btrfs
(rw,relatime,seclabel,ssd,space_cache,subvolid=318,subvol=/home)

-- 
Those who don't understand recursion are doomed to repeat it
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Broken btrfs filesystem

2012-01-10 Thread Peter Hjalmarsson
Hi,

I have problems with a btrfs filesystem, and am holding on to it for
some more days before reformat.
What I am interested about is two things:
1. Is there any way to restore more stuff from the filesystem then
already fetched (it would help to get the system up faster, but nothing
really of worth on that computer that is not already backed up)?
2. Is there anything here that resembles a bug that should be fixed
somewhere and do you need more information to fix this bug?

Please CC me as I am not subscribed.

So here comes the gory details:

I have a latop on which I have stock Fedora 16 installed with a ext4
boot, and then a luks-encrypted swap partiton and a luks-encrypted root
partition holding a btrfs volume.
Yesterday I hibernated my laptop, and when I resumed it it seemed to
resume normally, it let me unlock the screensaver, but did not allow any
file-system-access and suddenly oopsed within seconds. Afterwards the
system failed to mount the root partition.

So I hooked the harddrive up to my desktop running Gentoo with a
3.2.0-kernel and latest btrfs-progs from git.

Trying to mount the filesystem does not work:
[11353.370007] device fsid 4c86ad4c-0d71-48a3-8cd2-058cccda2a07 devid 1
transid
83234 /dev/mapper/udisks-luks-uuid-d7efe74d-ed8f-425a-942c-c6bbc44483a3-uid1000
[11353.391953] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391958] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391961] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391964] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391966] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391968] Failed to read block groups: -5
[11353.404931] btrfs: open_ctree failed


Trying with -o recovery
[11353.370007] device fsid 4c86ad4c-0d71-48a3-8cd2-058cccda2a07 devid 1
transid
83234 /dev/mapper/udisks-luks-uuid-d7efe74d-ed8f-425a-942c-c6bbc44483a3-uid1000
[11353.391953] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391958] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391961] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391964] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391966] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391968] Failed to read block groups: -5
[11353.404931] btrfs: open_ctree failed


So mounting it seems not to be an option.

So I tried restore.
First run it restored one file, then it stopped. Upon retrying it
restored a lot more files (mostly the /var/lib/yum directory, and a
couple of empty directories), but now it never restores more then up to
one certain file, and it always fails after that with the following:

# ./restore /dev/dm-1 /home/xake/Skrivbord/ferra-rescue
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
Ignoring transid failure
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
Ignoring transid failure
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
Ignoring transid failure
Root objectid is 5
Skipping existing
file /home/xake/Skrivbord/ferra-rescue/var/lib/rpm/.rpm.lock
If you wish to overwrite use the -o option to overwrite
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
Ignoring transid failure
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
Ignoring transid failure
parent transid verify failed on 823789125632 wanted 83120 found 83356
Ignoring transid failure
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
Ignoring transid failure
parent 

Broken btrfs filesystem

2012-01-10 Thread Peter Hjalmarsson
Hi,

I have problems with a btrfs filesystem, and am holding on to it for
some more days before reformat.
What I am interested about is two things:
1. Is there any way to restore more stuff from the filesystem then
already fetched (it would help to get the system up faster, but nothing
really of worth on that computer that is not already backed up)?
2. Is there anything here that resembles a bug that should be fixed
somewhere and do you need more information to fix this bug?

Please CC me as I am not subscribed.

So here comes the gory details:

I have a latop on which I have stock Fedora 16 installed with a ext4
boot, and then a luks-encrypted swap partiton and a luks-encrypted root
partition holding a btrfs volume.
Yesterday I hibernated my laptop, and when I resumed it it seemed to
resume normally, it let me unlock the screensaver, but did not allow any
file-system-access and suddenly oopsed within seconds. Afterwards the
system failed to mount the root partition.

So I hooked the harddrive up to my desktop running Gentoo with a
3.2.0-kernel and latest btrfs-progs from git.

Trying to mount the filesystem does not work:
[11353.370007] device fsid 4c86ad4c-0d71-48a3-8cd2-058cccda2a07 devid 1
transid
83234 /dev/mapper/udisks-luks-uuid-d7efe74d-ed8f-425a-942c-c6bbc44483a3-uid1000
[11353.391953] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391958] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391961] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391964] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391966] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391968] Failed to read block groups: -5
[11353.404931] btrfs: open_ctree failed


Trying with -o recovery
[11353.370007] device fsid 4c86ad4c-0d71-48a3-8cd2-058cccda2a07 devid 1
transid
83234 /dev/mapper/udisks-luks-uuid-d7efe74d-ed8f-425a-942c-c6bbc44483a3-uid1000
[11353.391953] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391958] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391961] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391964] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391966] parent transid verify failed on 869829160960 wanted 82376
found 83320
[11353.391968] Failed to read block groups: -5
[11353.404931] btrfs: open_ctree failed


So mounting it seems not to be an option.

So I tried restore.
First run it restored one file, then it stopped. Upon retrying it
restored a lot more files (mostly the /var/lib/yum directory, and a
couple of empty directories), but now it never restores more then up to
one certain file, and it always fails after that with the following:

# ./restore /dev/dm-1 /home/xake/Skrivbord/ferra-rescue
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
parent transid verify failed on 869829160960 wanted 82376 found 83320
Ignoring transid failure
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
parent transid verify failed on 869828055040 wanted 82376 found 83315
Ignoring transid failure
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
parent transid verify failed on 823939305472 wanted 83180 found 83847
Ignoring transid failure
Root objectid is 5
Skipping existing
file /home/xake/Skrivbord/ferra-rescue/var/lib/rpm/.rpm.lock
If you wish to overwrite use the -o option to overwrite
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
parent transid verify failed on 823805370368 wanted 83121 found 83393
Ignoring transid failure
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
parent transid verify failed on 823789125632 wanted 83120 found 83356
Ignoring transid failure
parent transid verify failed on 823789125632 wanted 83120 found 83356
Ignoring transid failure
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
parent transid verify failed on 823784792064 wanted 81189 found 83707
Ignoring transid failure
parent