解决挂载盘柜出现“EXT3-fs error filesystem read-only”

最新推荐文章于 2025-03-31 10:19:07 发布
最新推荐文章于 2025-03-31 10:19:07 发布 · 1.5k 阅读 · 2
文章标签：

#运维 #前端 #ViewUI

本文记录了一次Ext3文件系统出现问题导致分区被挂载为只读的情况，并详细介绍了使用fsck命令检查及重新格式化分区的修复过程。

昨天发现盘柜上的逻辑卷只能读，不能写！，查看盘柜管理页面，无错误提示，盘柜上面的硬盘指示灯也是正常的，查看前端的挂载机器的系统日志信息/var/log/messages，错误信息如下：
EXT3-fs error (device sdc1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_truncate: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_delete_inode: Journal has aborted
EXT3-fs warning (device sdb1): ext3_clear_journal_err: Filesystem error recorded from previous mount: IO failure
EXT3-fs warning (device sdb1): ext3_clear_journal_err: Marking fs in need of filesystem check.
EXT3-fs warning: mounting fs with errors, running e2fsck is recommended
EXT3 FS on sdb1, internal journal
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369513
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369514
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369515
EXT3-fs error (device sdc1): ext3_free_blocks_sb: bit already cleared for block 43369516
ext3_abort called.
EXT3-fs error (device sdc1): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_truncate: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sdc1) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sdc1) in ext3_delete_inode: Journal has aborted
从错误的信息来看，初步判断是由于ext3文件系统的日志引起的，当内核检测到ext3文件系统的日志有问题，就报警，严重的就将改分区挂载为只读模式。
下面开始着手解决这个问题：
1，首先用fsck检查改分区的文件系统 当用fsck命令检查该分区后，重新启动系统，系统还是报这样的错误。2，看来“病”的不轻，想过用第一张启动盘进入救援模式修复，但是一想，不对，没办 法识别到额外挂载的 设备，因为此时网络还有启动。3，看来只能用苯方法，将数据备份出来，重新格式化了，结果重新格式化后，解决问题。
总结：
文件系统损坏有几个原因，一个是非法关机，第二个是磁盘有环道，只能一个一个排除，先软后硬，如果格式化后，还是有问题，那原因多半就是硬件的问题了。同 时提醒兄弟们，多半的原因是由于非法关机引起的，比如冷启动，运气好的话，没有异常出现，否则，哈哈，你的麻烦来了。 希望兄弟们少走一些弯路，操作一定要规范！！！

EXT4修复FS error
Gavin Blog
09-10 1146
早起产品因为没有很多的控制cache flush策略，导致服务器掉电后，有比较高的概率出现EXT4 FS error，本文介绍借助 e2fsck 如何修复这部分错误。
linux内核 ext4,EXT4-fs error (device sdb4) ext4_find_entry...可能啥原因呢 - Linux内核技术 - KernelTech - 水木社区...
weixin_42362885的博客
04-30 2565
嗯，以下是昨天输出的结果。单纯看这个结果的话其实发现不了问题，因为没有记录任何明显的错误。但是跟其他节点对比，就会发现我上一个帖子说的问题(保留块相差一个量级)。#smartctl-x/dev/sdbsmartctl6.62016-05-31r4324[x86_64-linux-4.15.17-1-pve](localbuild)Copyright(C)2002-16,Br...
当文件系统变因为Detected aborted journal时filesystem read-only的解决方法
iteye_16035的博客
07-26 1724
真麻烦,一个机器有4个7T的存储中有二个存储有问题，用fsck修复了三次，都没有反应。使用使用着就提示下面的出错 #dmesg EXT3-fs error (device sdh1): ext3_journal_start_sb: Detected aborted journalRemounting filesystem read-onlyEXT3-fs error (device sdh1)...
EXT3-fs error
cool0528的博客
10-13 469
If your system abruptly loses power, or if a RAID card is beginning to fail, you might see an ominous mes...
EXT3-fs error故障
weixin_30737433的博客
11-02 1403
一。解决磁盘错误dmesg 报错：EXT3-fs error (device hda3) in start_transaction: Journal has abortedumount 出错分区后再mount磁盘修复：# e2fsck -y -C 0 /dev/sdc1 二。修改/oracle/dbs/initdbnms.ora文件*.undo_management='AUTO'_allow_r...
Authorized users only. All activities may be monitored and reported. Activate the web console with: systemctl enable --now cockpit.socket ZXSK-YSYC-7 login: [10999.689621] print_req_error: I/O error, dev sda, sector 0 [11000.318378] Buffer I/O error on device dm-0, logical block 111214090 [11001.193689] Buffer I/O error on device dm-0, logical block 111214091 [11001.203070] Buffer I/O error on device dm-0, logical block 111214092 [11004.805762] Buffer I/O error on device dm-0, logical block 108572673 [11004.805809] Aborting journal on device dm-0-8. [11004.816519] EXT4-fs (dm-0): ext4_writepages: jbd2_start: 832 pages, ino 27131915; err -30 [11004.816522] Buffer I/O error on dev dm-0, logical block 70811648, lost sync page write [11004.824662] EXT4-fs error (device dm-0): ext4_journal_check_start:61: comm kworker/u129:1: Detected aborted journal [11004.842929] JBD2: Error -5 detected when updating journal superblock for dm-0-8. [11004.850308] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [11004.857585] EXT4-fs (dm-0): I/O error while writing superblock [11004.863393] EXT4-fs (dm-0): Remounting filesystem read-only [11004.868947] EXT4-fs (dm-0): ext4_writepages: jbd2_start: 832 pages, ino 27132119; err -30 [11155.075123] Aborting journal on device sda2-8. [11155.079558] Buffer I/O error on dev sda2, logical block 131072, lost sync page write [11155.087270] JBD2: Error -5 detected when updating journal superblock for sda2-8. [11160.128455] FAT-fs (sda1): Directory bread(block 408) failed [11160.134102] FAT-fs (sda1): Directory bread(block 409) failed [11160.139747] FAT-fs (sda1): Directory bread(block 410) failed [11160.145386] FAT-fs (sda1): Directory bread(block 411) failed [11160.151023] FAT-fs (sda1): Directory bread(block 412) failed [11160.156659] FAT-fs (sda1): Directory bread(block 413) failed [11160.162295] FAT-fs (sda1): Directory bread(block 414) failed [11160.167931] FAT-fs (sda1): Directory bread(block 415) failed [11160.173567] FAT-fs (sda1): Directory bread(block 416) failed [11160.179203] FAT-fs (sda1): Directory bread(block 417) failed [11226.300023] FAT-fs (sda1): Directory bread(block 408) failed [11226.305671] FAT-fs (sda1): Directory bread(block 409) failed [11226.311316] FAT-fs (sda1): Directory bread(block 410) failed [11226.316955] FAT-fs (sda1): Directory bread(block 411) failed [11226.322595] FAT-fs (sda1): Directory bread(block 412) failed [11226.328231] FAT-fs (sda1): Directory bread(block 413) failed [11226.333867] FAT-fs (sda1): Directory bread(block 414) failed [11226.339503] FAT-fs (sda1): Directory bread(block 415) failed [11226.345139] FAT-fs (sda1): Directory bread(block 416) failed [11226.350774] FAT-fs (sda1): Directory bread(block 417) failed [11337.344788] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [11337.353219] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [11337.360501] EXT4-fs (dm-0): I/O error while writing superblock [11352.343658] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [11352.352085] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [11352.359366] EXT4-fs (dm-0): I/O error while writing superblock [11368.559373] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [11368.567805] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [11368.575085] EXT4-fs (dm-0): I/O error while writing superblock [18387.542842] Buffer I/O error on dev dm-0, logical block 144, async page read [18387.549869] Buffer I/O error on dev dm-0, logical block 145, async page read [18387.556890] Buffer I/O error on dev dm-0, logical block 146, async page read [18387.563912] Buffer I/O error on dev dm-0, logical block 147, async page read [18387.570933] Buffer I/O error on dev dm-0, logical block 148, async page read [18387.577952] Buffer I/O error on dev dm-0, logical block 149, async page read [18387.584971] Buffer I/O error on dev dm-0, logical block 150, async page read [18387.591991] Buffer I/O error on dev dm-0, logical block 151, async page read [18387.599010] Buffer I/O error on dev dm-0, logical block 152, async page read [18387.606029] Buffer I/O error on dev dm-0, logical block 153, async page read [19773.911150] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.922389] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.933490] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19773.935741] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.940773] EXT4-fs (dm-0): I/O error while writing superblock [19773.952047] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.957664] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19773.968823] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.976016] EXT4-fs (dm-0): I/O error while writing superblock [19773.976023] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19773.987135] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19773.992903] EXT4-fs (dm-0): I/O error while writing superblock [19773.992910] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.000204] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19774.011259] EXT4-fs (dm-0): I/O error while writing superblock [19774.011265] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.017177] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19774.024344] EXT4-fs (dm-0): I/O error while writing superblock [19774.024350] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.035445] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19774.041230] EXT4-fs (dm-0): I/O error while writing superblock [19774.041237] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.048691] EXT4-fs error (device dm-0): ext4_find_entry:1514: inode #27131979: comm journalctl: reading directory lblock 0 [19774.059586] EXT4-fs (dm-0): I/O error while writing superblock [19774.059592] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.120993] EXT4-fs (dm-0): I/O error while writing superblock [19774.126808] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [19774.134087] EXT4-fs (dm-0): I/O error while writing superblock [278024.971840] Buffer I/O error on dev dm-0, logical block 1120, async page read [278024.979040] Buffer I/O error on dev dm-0, logical block 1121, async page read [278024.986234] Buffer I/O error on dev dm-0, logical block 1122, async page read [278024.993427] Buffer I/O error on dev dm-0, logical block 1123, async page read [278025.000619] Buffer I/O error on dev dm-0, logical block 1124, async page read [278025.007812] Buffer I/O error on dev dm-0, logical block 1127, async page read [278025.015004] Buffer I/O error on dev dm-0, logical block 1128, async page read [278025.022197] Buffer I/O error on dev dm-0, logical block 1129, async page read [278025.029389] Buffer I/O error on dev dm-0, logical block 1130, async page read [278025.036581] Buffer I/O error on dev dm-0, logical block 1131, async page read [279478.949021] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [279478.957544] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [279478.964911] EXT4-fs (dm-0): I/O error while writing superblock [280325.696604] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [280325.705122] Buffer I/O error on dev dm-0, logical block 0, lost sync page write [280325.712488] EXT4-fs (dm-0): I/O error while writing superblock [280361.819944] EXT4-fs error (device dm-0): ext4_remount:5658: comm mount: Abort forced by user [280361.828450] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
07-16
### 三级标题：EXT4文件系统超级块写入错误的诊断与修复 EXT4文件系统的超级块包含关键的元数据信息，如文件系统大小、空闲空间、inode分配状态等。当内核报告`I/O error while writing superblock`时，通常意味着...
(kali+ kali)-[M) > ss[ 5357.232911] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083: lnode #311358: lblock di su r[ 5358.010620] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083:inode #311358:1block din din o[ 5358.177984] EXT4-fs wanning (device sdc2):htree_dirblock_to_tree:1083:lnode #311358： lblock readin ector 于等于号 o! 5358.339999] EXT4-fs warning (device sdc2):htree_dlrblock_to_tree:1083:Lnode #311358: Iblock eaciin ector bloc 5358.607975 EXT4-fs warning (device sdc2):htree_dlrblock_to_tree:103: inode 311958:i Iblock ector Ja 5360.9174791 EXT4-fs warning (device sdc2):htree_dlrblock_to_tree:1083:Inode #311358:1 Iblock ector 业 5361.137485] EXT4-fs warning (device sdc2): htree_dirblock_to_tree:1083: 1node #311358： lblock neadins ector lac 5361.307507] htree_dirblock_to_tree:1083:inode #311358： lblock eadin ector 5361.474242] 1 eadins ector! 64 5364.149505 5364.30353311 EXT4-fs warning (device sdc2):htree_dirblock_to_tree:103: inode 311358:1 lblock adin ector To eading 5366.848535] EXT4-fs warning ( eadin eading el 5367.286539] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083: lnode 311358:161ock reading 5369.292697] 1 ectory rector 5369.372716] 1 5369.412683]1 5969.4526901 rector 5369.535569] 0: ector 5369.742561] EXTA-fs warning (devlce sdce):htree_dlnblock_to_tree:10631 0: 5369.921570]1 5370.108566] 1 [5370.278258] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083:inode #311358:Iblock e: c[ 5378, 767092] EXT4-fs warning:2 callbacks suppressed 5378.767095] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1063 inode #311358:_1block e: comm zsh; error -5 actory bloc coc[ 5379.061001] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083:lnode *311358:1block 0; comm zsh: error -5 director cccc[5379.101710] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083:Lnode #311358:Iblock 0: cOmm zsh: error nnnnín ínn -5 dir ecto cc[ 5379,141255] EXT4-fs warning (device sdc2)； htree_dirblock_to_tree:1083:inode #311358:1block 0: comm zsh; !!!!!!! reading rectory 8888 [ 5379.161160] EXT4-fs warning ( (device sdc2)； 03 COI ectors 5379.599427] 1 EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083:inode Iblock 0: COM m rectors 5379.853287] EXT4-fs warning ( #311358； Iblock CO 号号号! ectory [ 5379.893262] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:103:1node 1 #311358；] Iblock com rectory 288 5379.933280] EXT4-fs uarning ( (device sdc2);htree_dirblock_to_tree:1083： inode #311358； Iblock Q3 rector [ 5379.973203] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083: Inode #311358：1block 03 rector [5383, 771595】 EXT4-fs warning:22 callbacks suppressed [5383.771598] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1083: Lnode #311358 1block 0: en -5 dir 号号号号号号号号号 ectory 1532742721 [ 5385.118592] EXT4-fs warning (device sdc2):htree_dirblock_to_tree:1069: inode #311358； lblock 出会会会 EXT4-fs swarning( (device sdc2): htree_dirblock_to_tree:1083；. Inode #311358；] Iblock [ 5385.635316] EXT4-fs warning( (device sdc2); htree_dirblock_to_tree:1083； inode #3113581 Iblock ector 5386.991309] EXT4-fs swarning (device sdc2); htree_dirblock_to_tree:1083； inode #311358； Iblock rector 5387.0759541 EXT4-fs warning sdc2 2)； htree_dirblock_to_tree:1083; inode N311358： 1block ector 5387, 219259] EXT4-fs aning )； htree_dirb lock_to_tree:10033 Lnode #3113581 Iblock 5387.506792] EXT4-fs device htree_dirbl lock_to_treei1003: Ma11858i 1block 5388.0553401 EXT4-fs dei ice htree_dirb lock .to_tree 10831 1B18% 5388.061712] EXT4-fs Cdevice htree_dirblock_to_tree:1083 打不了字是啥原因
最新发布
10-03
我们注意到用户的问题是关于Kali系统出现EXT4-fs警告且无法打字的情况。根据用户提供的引用内容，虽然引用主要涉及源配置和软件包安装问题，但我们可以结合文件系统错误和输入故障的一般处理方法进行分析。 问题...
[ 20.868097]0EXT4-fs (sda2): unabe to read supetb lock
04-14
如果提示"filesystem mounted read-only"，需先卸载分区： ```bash umount /dev/sda2 ``` 再执行修复。若无法卸载，可尝试强制修复： ```bash sudo e2fsck -f -y /dev/sda2 ``` #### 2. 使用备份超级块 EXT4文件...
linux自动挂载文件修复工具,Linux FSCK自动修复文件系统
weixin_28764585的博客
05-09 1598
背景：Linux系统(Ubuntu)在运行时，断电等非正常关机操作，会导致ext4文件系统数据损坏。严重时会导致系统崩溃。如下log就是系统数据损坏。[ 7.878756] EXT4-fs error (device mmcblk0p2): ext4_mb_generate_buddy:742: group 0, 14845 clusters in bitmap, 14822 in gd[ ...
mkfs.ext4 -- 生成ext4文件系统
m0_51451952的博客
06-19 4332
论如何生成ext4文件系统文件
EXT3-fs error ( device sd(8,5)) in start_transaction:Journal has aborted
cuixie2370的博客
01-14 356
Red Hat Linux AS3.0 U6 , DELL 2950 Oracle RAC , 9.2.0.7 , OCFS , RAC , 双节点 今天11点左右发现 NODE02 中的 ...
kernel: EXT3-fs error (device sdb1) in start_transaction: Journal has aborted
cuixie2370的博客
03-05 617
Red Hat Enterprise Linux AS release 4 (Nahant)Kernel 2.6.9-5.ELsmp on an i686 /bin/login: error while loading sha...
EXT3-fs error(device hda3) in start_transaction:Journal has aborted linux
lidongtang的专栏
12-20 4591
RedHat 4 重启机器出现 EXT3-fs error(device hda3) in start_transaction:Journal has aborted  进入不了系统，强制关闭机器后，再次重启进入到了repair filesystem fsch  /dev/VolGroup00/LogVol00 一直按回车，终于把文件系统修复好 reboot后，机器能正常启动 出现磁盘
EXT3-fs error和EXT4-fs error小总结
热门推荐
喜欢打篮球的普通人
02-05 1万+
文章目录1.出现问题时的解决办法 1.出现问题时的解决办法 查看OS的日志/var/log/messages，应该会有相关的报错信息 对于ext3类型的文件系统，可以使用tune2fs 查看 tune2fs -l /dev/sdf|grep stat Filesystem state: clean 使用fsck命令来检测和修复文件系统，FSCK 全称为 File System Consistency Check 作用： 它可以进行三种模式的操作， 查错并在发现错误时由用户决定
Ext3.x中的readOnly配置项
老李 技术 专栏
03-10 2066
我接触Ext是从2.0版本开始的，在一家公司做移动项目，他们已经将Ext的代码大部分标签化了，刚开始觉得不习惯，不过现在想想的确封装的很强大。    这段时间一直在研究3.x版本，我承认我被它的新特性吸引住了，当然，吸引我的不仅仅是这些新特性，在性能和执行效率上也有改良和提高。    但昨天碰到了一个棘手的问题，在2.0版本中，dateField和comboBox两个组件，有一个配置项叫r
LINUX系统磁盘FC-SAN ext3系统突然变位只读了
cri5768的博客
01-21 252
日志如下： Jan 21 03:38:20 D0-LNXAPP03 kernel: SCSI error : <0 0 0 2> return code = 0x20000Jan 21 03:38:20 D0-LN...
ext 元素只读
sansan的地盘
04-27 452
this.el.dom.readOnly = true;
ext4fs error mysql_请教一个 Linux 挂在磁盘阵列报错 EXT4-fs error 问题
weixin_40003780的博客
01-27 7979
从昨天开始 linux 通过光纤直接连接磁盘阵列，会出现磁盘阵列掉了的情况，然后机器会重启，本来重启后，rose ha 会自动挂载磁盘阵列，现在由于 rose ha 也出了点问题，导致不切换备用服务器，主服务器也不挂载磁盘阵列的情况。导致服务起不来。目前报错如下 EXT4-fs error (device sdb): ext4_read_block_bitmap: Cannot read bloc...
fs-err：更友好的文件操作错误处理
gitblog_00480的博客
03-31 623
fs-err：更友好的文件操作错误处理 项目介绍 在现代软件开发中，文件操作是基础且频繁的任务。但在处理文件时，错误处理往往是一件令人头疼的事情。fs-err 是一个针对 Rust 语言的标准库 std::fs 的替代品，它提供了更详细的错误信息，帮助开发者快速定位和解决问题。fs-err 通过增加操作描述和路径信息，使得错误消息更加直观和有用。 项目技术分析 fs-err 的核心是对 Rust ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值