summaryrefslogtreecommitdiff
path: root/scripts/lib/kdoc/kdoc_files.py
diff options
context:
space:
mode:
authorQu Wenruo <wqu@suse.com>2024-12-10 07:53:06 +0300
committerDavid Sterba <dsterba@suse.com>2025-01-13 16:53:15 +0300
commitd0f038104fa37380e2a725e669508e43d0c503e9 (patch)
treee849eb2375a3e6535ae2df5868709a725aed4e8e /scripts/lib/kdoc/kdoc_files.py
parenta883120b2d19630d3be56bc9649a71299ccbf95d (diff)
downloadlinux-d0f038104fa37380e2a725e669508e43d0c503e9.tar.xz
btrfs: output the reason for open_ctree() failure
There is a recent ML report that mounting a large fs backed by hardware RAID56 controller (with one device missing) took too much time, and systemd seems to kill the mount attempt. In that case, the only error message is: BTRFS error (device sdj): open_ctree failed There is no reason on why the failure happened, making it very hard to understand the reason. At least output the error number (in the particular case it should be -EINTR) to provide some clue. Link: https://lore.kernel.org/linux-btrfs/9b9c4d2810abcca2f9f76e32220ed9a90febb235.camel@scientia.org/ Reported-by: Christoph Anton Mitterer <calestyo@scientia.org> Cc: stable@vger.kernel.org Reviewed-by: Filipe Manana <fdmanana@suse.com> Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_files.py')
0 files changed, 0 insertions, 0 deletions