Bug 16137

Summary: Ooops in BTRFS in 2.6.34 / x86_64 when mounting subvolume by name
Product: File System Reporter: Maciej Rutecki (maciej.rutecki)
Component: btrfsAssignee: fs_btrfs (fs_btrfs)
Status: CLOSED INSUFFICIENT_DATA    
Severity: normal CC: brian, maciej.rutecki, mick, rjw
Priority: P1    
Hardware: All   
OS: Linux   
Kernel Version: 2.6.34 Subsystem:
Regression: Yes Bisected commit-id:
Bug Depends on:    
Bug Blocks: 15310    

Description Maciej Rutecki 2010-06-06 06:06:16 UTC 
Subject    : Ooops in BTRFS in 2.6.34 / x86_64 when mounting subvolume by name
Submitter  : armin walland <a.walland@focusmr.com>
Date       : 2010-05-27 12:27
Message-ID : 201005271428.01239.a.walland@focusmr.com
References : http://marc.info/?l=linux-kernel&m=127496434110736&w=2

This entry is being used for tracking a regression from 2.6.33.  Please don't
close it until the problem is fixed in the mainline.
Comment 1 Brian Rogers 2010-08-01 17:52:07 UTC 
He runs set-default for his /v_root subvolume, then tries to mount /v_home. But strangely, the subvol= mount option works relative to the default subvolume, not the root. So he can't reach /v_home that way. He's trying to mount a nonexistent path.

The real bug is that it crashes if you try to mount a nonexistent subvolume.
Comment 2 Mck 2010-10-01 20:26:07 UTC 
Sure it won't be successful but it crashes the module and forces the user to have to restart.
Comment 3 Mck 2010-10-01 20:28:39 UTC 
And i still get this in 2.6.35